Re: [systemd-devel] Trying to come up with udev rule for USB geographic naming

11.07.2017 05:33, Paul D. DeRocco пишет: > That is, I want a rule for creating a symlink that describes the USB port > something is plugged into, rather than the specific device plugged into > it. Linux USB has a way of representing the location of each physical > jack, even when hubs are

[systemd-devel] systemd-networkd not sending DHCP v6 requests

I'm playing using systemd-networkd (rather than the legacy network service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing interface once chrony is synced" thread for background.) I have "DHCP=yes" in the [Network] section of my WAN interface (eth0.256.network): [Match] Name=eth0.256

[systemd-devel] Trying to come up with udev rule for USB geographic naming

That is, I want a rule for creating a symlink that describes the USB port something is plugged into, rather than the specific device plugged into it. Linux USB has a way of representing the location of each physical jack, even when hubs are involved. For devices like USB serial and USB MIDI, I'd

Re: [systemd-devel] Unknown lvalue 'StartLimitIntervalSec' ?

Aha! Many thanks Zbyszek On 11 July 2017 at 02:26, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Jul 11, 2017 at 01:55:21AM +0100, Neil MacLeod wrote: > > I see that with the following commit, 'StartLimitInterval' is aliased to > > 'StartLimitIntervalSec': > > > >

Re: [systemd-devel] Unknown lvalue 'StartLimitIntervalSec' ?

On Tue, Jul 11, 2017 at 01:55:21AM +0100, Neil MacLeod wrote: > I see that with the following commit, 'StartLimitInterval' is aliased to > 'StartLimitIntervalSec': > > https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a#diff-b3e16bf39e5d7ab233077b9b1dafb095 > >

[systemd-devel] Unknown lvalue 'StartLimitIntervalSec' ?

I see that with the following commit, 'StartLimitInterval' is aliased to 'StartLimitIntervalSec': https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a#diff-b3e16bf39e5d7ab233077b9b1dafb095 This change should be in systemd-230. However, using 'StartLimitIntervalSec`

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

On Mon, Jul 10 2017, Steve Dickson wrote: > Hey Neil, > > On 07/04/2017 06:20 PM, NeilBrown wrote: >> On Tue, May 30 2017, NeilBrown wrote: >> >>> Systemd does not, and will not, support "bg" correctly. >>> It has other, better, ways to handle "background" mounting. >> >> For those who aren't

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Sat, Jul 08, 2017 at 03:49:11AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Jul 07, 2017 at 03:54:09PM -0700, vcap...@pengaru.com wrote: > > On Fri, Jul 07, 2017 at 10:34:22PM +, Zbigniew Jędrzejewski-Szmek wrote: > > > On Fri, Jul 07, 2017 at 02:35:16PM -0700, vcap...@pengaru.com

Re: [systemd-devel] Bouncing interface once chrony is synced

On Mon, Jul 10, 2017 at 7:03 PM, Julian Andres Klode wrote: > On Wed, Jul 05, 2017 at 10:29:21AM -0500, Ian Pilcher wrote: > > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > > firewall/gateway. The Banana Pi does not have a persistent clock, so > > it has

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 17:45, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > On Mon, Jul 10, 2017 at 06:40:00PM +0200, Lennart Poettering wrote: > > On Mon, 10.07.17 18:36, Lennart Poettering (lenn...@poettering.net) wrote: > > > > > > After all (as other people said) systemd has no such

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 06:40:00PM +0200, Lennart Poettering wrote: > On Mon, 10.07.17 18:36, Lennart Poettering (lenn...@poettering.net) wrote: > > > > After all (as other people said) systemd has no such requirements > > > itself. It is true that such user names are confusing and > > >

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 15:29, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > On current Fedora, the current regex useradd enforces appears to be > > this: > > > > [a-zA-Z0-9._][a-zA-Z0-9._-]{0,30}[a-zA-Z0-9._-$]? > > > > If I read things correctly at least... (the trailing $ appears

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 18:36, Lennart Poettering (lenn...@poettering.net) wrote: > > After all (as other people said) systemd has no such requirements > > itself. It is true that such user names are confusing and > > non-portable, but if the local admin has or wants to have such an > > account for

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 4:03 PM, Lennart Poettering wrote: > On current Fedora, the current regex useradd enforces appears to be > this: > > [a-zA-Z0-9._][a-zA-Z0-9._-]{0,30}[a-zA-Z0-9._-$]? So, it *does* allow for usernames starting with numbers...

Re: [systemd-devel] Bouncing interface once chrony is synced

On 07/10/2017 03:43 AM, Lennart Poettering wrote: If your DHCP client implementation gets confused by the wallclock not being steady then this appears to be a bug in the implementation. Given that there are so many DHCP clients to choose from, maybe use a different one? Oh, it's definitely a

Re: [systemd-devel] Bouncing interface once chrony is synced

On Wed, Jul 05, 2017 at 10:29:21AM -0500, Ian Pilcher wrote: > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > firewall/gateway. The Banana Pi does not have a persistent clock, so > it has no idea what the time is until it is able to sync via NTP. Thus, > the initial DHCP

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

Hey Neil, On 07/04/2017 06:20 PM, NeilBrown wrote: > On Tue, May 30 2017, NeilBrown wrote: > >> Systemd does not, and will not, support "bg" correctly. >> It has other, better, ways to handle "background" mounting. > > For those who aren't closely watching systemd development, a > patch was

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 05:03:09PM +0200, Lennart Poettering wrote: > On Mon, 10.07.17 22:23, Michael Chapman (m...@very.puzzling.org) wrote: > > > > Well, it took 3 years or so, until someone noticed the strict rules we > > > enforce. I seriously doubt that naming system users in such unsafe > >

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 22:23, Michael Chapman (m...@very.puzzling.org) wrote: > > Well, it took 3 years or so, until someone noticed the strict rules we > > enforce. I seriously doubt that naming system users in such unsafe > > ways is really that wide-spread usage. > > That _could_ be because people

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 15:58, Lennart Poettering (lenn...@poettering.net) wrote: > On Mon, 10.07.17 15:16, Jan Synacek (jsyna...@redhat.com) wrote: > > > On Mon, Jul 10, 2017 at 12:42 PM, Lennart Poettering > > wrote: > > > Now, because this is so weakly defined, we hence do

Re: [systemd-devel] Github systemd issue 6237

Am Montag, den 10.07.2017, 12:57 +0200 schrieb Reindl Harald: > > Am 10.07.2017 um 12:55 schrieb Lennart Poettering: > > > > > > The "nobody" user has special semantics on Linux: it's where things > > are mapped to that can't be mapped otherwise. It's used by user > > namspacing, by NFS and

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 15:16, Jan Synacek (jsyna...@redhat.com) wrote: > On Mon, Jul 10, 2017 at 12:42 PM, Lennart Poettering > wrote: > > Now, because this is so weakly defined, we hence do not follow POSIX > > rules, but filter out more that might be dangerous. Specifically:

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 12:42 PM, Lennart Poettering wrote: > Now, because this is so weakly defined, we hence do not follow POSIX > rules, but filter out more that might be dangerous. Specifically: > > 1. We do not permit empty usernames > 2. We don't permit the first

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10 Jul 2017, Lennart Poettering wrote: On Mon, 10.07.17 21:15, Michael Chapman (m...@very.puzzling.org) wrote: Now, I do think that systemd has the duty to complain about any system user names outside of the safe range. Not only for security reasons, but also for portability and

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Mon, 10 Jul 2017, Lennart Poettering wrote: On Mon, 10.07.17 21:51, Michael Chapman (m...@very.puzzling.org) wrote: This all stems from my experiences with PulseAudio back in the day: People do not grok the effect of fork(): it only duplicates the invoking thread, not any other threads of

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Mon, 10.07.17 21:51, Michael Chapman (m...@very.puzzling.org) wrote: > > This all stems from my experiences with PulseAudio back in the day: > > People do not grok the effect of fork(): it only duplicates the > > invoking thread, not any other threads of the process, moreover all > > data

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Mon, 10 Jul 2017, Lennart Poettering wrote: On Sat, 08.07.17 16:24, Michael Chapman (m...@very.puzzling.org) wrote: On Sat, 8 Jul 2017, vcap...@pengaru.com wrote: In doing some casual journalctl profiling and stracing, it became apparent that `journalctl -b --no-pager` runs across a

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10.07.17 21:15, Michael Chapman (m...@very.puzzling.org) wrote: > > Now, I do think that systemd has the duty to complain about any system > > user names outside of the safe range. Not only for security reasons, > > but also for portability and compatibility reasons: I think we should > >

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Sat, 08.07.17 16:24, Michael Chapman (m...@very.puzzling.org) wrote: > On Sat, 8 Jul 2017, vcap...@pengaru.com wrote: > > In doing some casual journalctl profiling and stracing, it became apparent > > that `journalctl -b --no-pager` runs across a significant quantity of logs, > > ~10% of the

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Fri, 07.07.17 14:35, vcap...@pengaru.com (vcap...@pengaru.com) wrote: > On Fri, Jul 07, 2017 at 01:49:54PM -0700, vcap...@pengaru.com wrote: > > On Fri, Jul 07, 2017 at 08:37:08PM +, Mantas Mikulėnas wrote: > > > Back when that commit was made, didn't glibc cache the getpid() result in > >

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10 Jul 2017, Lennart Poettering wrote: On Thu, 06.07.17 13:21, Michael Chapman (m...@very.puzzling.org) wrote: On Thu, 6 Jul 2017, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Jul 06, 2017 at 01:43:32AM +0200, Reindl Harald wrote: well, it even don't look but pretend it can't while it

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On Mon, 10 Jul 2017 12:47:24 +0200, Peter Rajnoha wrote: > On 07/10/2017 12:14 PM, Peter Rajnoha wrote: ... > > Yes, please, any rules for symlinks which should be created under > > /dev/disk for DM devices (including all its subsystems like LVM, > > mpath...) should go into 13-dm-disk.rules that

Re: [systemd-devel] Github systemd issue 6237

On Mon, 10 Jul 2017, Lennart Poettering wrote: On Thu, 06.07.17 09:36, Michael Chapman (m...@very.puzzling.org) wrote: User=0day fails a syntactic validation, not a semantic validation. systemd never even checks to see whether the user exists when the unit is loaded. And nor should it! The

Re: [systemd-devel] Github systemd issue 6237

Am 10.07.2017 um 12:42 schrieb Lennart Poettering: (I do accept though that it's a valid discussion whether systemd's current behaviour of warning and skipping invalid User= rvalues is the best choice, instead of erroring out completely.) and *that* is the real point of the whole issue - if

Re: [systemd-devel] Github systemd issue 6237

Am 10.07.2017 um 12:55 schrieb Lennart Poettering: On Thu, 06.07.17 10:34, Reindl Harald (h.rei...@thelounge.net) wrote: Am 06.07.2017 um 09:59 schrieb Jonathan de Boyne Pollard: Reindl Harald: > at least fall back to “nobody” Jonathan de Boyne Pollard: > That idea is wrong. > >

Re: [systemd-devel] Github systemd issue 6237

On Thu, 06.07.17 10:34, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 06.07.2017 um 09:59 schrieb Jonathan de Boyne Pollard: > > Reindl Harald: > > > at least fall back to “nobody” > > > > Jonathan de Boyne Pollard: > > > That idea is wrong. > > > > > >

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On 07/10/2017 12:14 PM, Peter Rajnoha wrote: > On 07/10/2017 11:53 AM, Lennart Poettering wrote: >> On Mon, 10.07.17 11:37, David Disseldorp (dd...@suse.de) wrote: >> >>> Thanks for the feedback, Lennart... >>> >>> On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote: >>> On Wed,

Re: [systemd-devel] Github systemd issue 6237

On Thu, 06.07.17 09:36, Michael Chapman (m...@very.puzzling.org) wrote: > User=0day fails a syntactic validation, not a semantic validation. systemd > never even checks to see whether the user exists when the unit is loaded. > And nor should it! The user must be allowed to not exist at unit-load

Re: [systemd-devel] Github systemd issue 6237

On Thu, 06.07.17 13:21, Michael Chapman (m...@very.puzzling.org) wrote: > On Thu, 6 Jul 2017, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Jul 06, 2017 at 01:43:32AM +0200, Reindl Harald wrote: > > > well, it even don't look but pretend it can't while it does which is > > > the worst type of

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On 07/10/2017 11:53 AM, Lennart Poettering wrote: > On Mon, 10.07.17 11:37, David Disseldorp (dd...@suse.de) wrote: > >> Thanks for the feedback, Lennart... >> >> On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote: >> >>> On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote:

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On Mon, 10.07.17 11:37, David Disseldorp (dd...@suse.de) wrote: > Thanks for the feedback, Lennart... > > On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote: > > > On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote: > > > > > Ceph relies on by-partuuid symlinks, in order

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

Thanks for the feedback, Lennart... On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote: > On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote: > > > Ceph relies on by-partuuid symlinks, in order to locate the journal > > partition from a given OSD partition. For details,

Re: [systemd-devel] mkosi.postinst and user home permissions

Il giorno lun 10 lug 2017 alle 10:46, Lennart Poettering ha scritto: On Tue, 04.07.17 12:28, Federico Bruni (f...@inventati.org) wrote: I'm building fedora-26 in a directory. I want to add a normal user, so I've added to mkosi.postinst: useradd dev -p mypassword

Re: [systemd-devel] Is there a reason to run systemd Units with root access?

On Tue, 04.07.17 20:33, Mariusz Wojcik (m6woj...@outlook.com) wrote: > Hi, > > I’m just asking because of the latest “not-a-bug” [1]. As far as I > know, there aren’t many services that need full root access (maybe > for getting a low port number). Except for that I don’t see many use > cases.

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On Mon, Jul 10, 2017 at 10:38:38AM +0200, Lennart Poettering wrote: > On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote: > > > Ceph relies on by-partuuid symlinks, in order to locate the journal > > partition from a given OSD partition. For details, see > >

Re: [systemd-devel] Is there a reason to run systemd Units with root access?

Am 10.07.2017 um 10:49 schrieb Lennart Poettering: On Tue, 04.07.17 20:33, Mariusz Wojcik (m6woj...@outlook.com) wrote: Hi, I’m just asking because of the latest “not-a-bug” [1]. As far as I know, there aren’t many services that need full root access (maybe for getting a low port number).

Re: [systemd-devel] mkosi.postinst and user home permissions

On Tue, 04.07.17 12:28, Federico Bruni (f...@inventati.org) wrote: > Hi all > > I hope this is the right place to ask questions about mkosi. Hmm, not really. We currently have no mailing list for mkosi though. Maybe the github issue tracker of mkosi would be the best place to discuss things

Re: [systemd-devel] [PATCH] rules: block - add dm devices to whitelist

On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote: > Ceph relies on by-partuuid symlinks, in order to locate the journal > partition from a given OSD partition. For details, see > http://tracker.ceph.com/issues/19489. This appears way too broad, as it would apply to all LVM and all

Re: [systemd-devel] Bouncing interface once chrony is synced

On Wed, 05.07.17 10:29, Ian Pilcher (arequip...@gmail.com) wrote: > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > firewall/gateway. The Banana Pi does not have a persistent clock, so > it has no idea what the time is until it is able to sync via NTP. Thus, > the initial

Re: [systemd-devel] Realtime scheduling with CONFIG_RT_GROUP_SCHED=y

On Thu, 06.07.17 10:56, Lars Kellogg-Stedman (l...@redhat.com) wrote: > I'm running on a kernel with CONFIG_RT_GROUP_SCHED=y. I understand that > this is counter to the recommendation in the README ("We recommend to turn > off Real-Time group scheduling in the kernel when using systemd"),