Re: [systemd-devel] Github systemd issue 6237

2017-07-06 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jul 05, 2017 at 08:10:15PM +1000, Michael Chapman wrote: > On Wed, 5 Jul 2017, Colin Guthrie wrote: > >Reindl Harald wrote on 04/07/17 19:50: > >>>When new configuration options are added, the same unit file can > >>>almost always be used with older systemd, and it'll just warn & ignore >

Re: [systemd-devel] Github systemd issue 6237

2017-07-06 Thread Oliver Neukum
Am Mittwoch, den 05.07.2017, 20:10 +1000 schrieb Michael Chapman: > I'm pretty sure you'll find that it does. Specifically, it will fail when > the child process for the command being executed attempts to map the > username to a UID. > > The issue being discussed here is that systemd considers

Re: [systemd-devel] Github systemd issue 6237

2017-07-06 Thread Jonathan de Boyne Pollard
Reindl Harald: > at least fall back to “nobody” Jonathan de Boyne Pollard: > That idea is wrong. > > https://news.ycombinator.com/item?id=14681377#14682059 Reindl Harald: > better than a stupid [...] Not really, no. It's the same category of error, in fact: substituting an account other than

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

2017-07-06 Thread Reindl Harald
Am 04.07.2017 um 22:33 schrieb Mariusz Wojcik: 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. Therefore, I think it would be

Re: [systemd-devel] Github systemd issue 6237

2017-07-06 Thread Reindl Harald
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. > > https://news.ycombinator.com/item?id=14681377#14682059 Reindl Harald: > better than a stupid [...] Not really, no. It's the

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

2017-07-06 Thread Simon McVittie
On Tue, 04 Jul 2017 at 20:33:54 +, Mariusz Wojcik wrote: > As far as I know, there > aren’t many services that need full root access (maybe for getting a low port > number). systemd system units are basically a replacement for LSB (or sysvinit if you prefer) init scripts, which always run as

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

2017-07-06 Thread Mariusz Wojcik
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. Therefore, I think it would be useful to make the decision for root access more

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

2017-07-06 Thread Michael Chapman
On Wed, 5 Jul 2017, Mariusz Wojcik 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. Therefore, I think it would be

Re: [systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Michael Chapman
On Thu, 6 Jul 2017, Mikhail Kasimov wrote: Hello! 've got an interesting trouble on timer-activated service -- 'systemctl status' returns a log with 'Activating (start)' status: [1] == k_mikhail@linux-mk500:~> systemctl status vba32update.service ● vba32update.service - VBA32

[systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Mikhail Kasimov
Hello! 've got an interesting trouble on timer-activated service -- 'systemctl status' returns a log with 'Activating (start)' status: [1] == k_mikhail@linux-mk500:~> systemctl status vba32update.service ● vba32update.service - VBA32 Anti-Virus Update Service Loaded: loaded

Re: [systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Michael Chapman
On Fri, 7 Jul 2017, Mikhail Kasimov wrote: 06.07.2017 17:18, Michael Chapman пишет: On Thu, 6 Jul 2017, Mikhail Kasimov wrote: Hello! 've got an interesting trouble on timer-activated service -- 'systemctl status' returns a log with 'Activating (start)' status: [1] ==

[systemd-devel] Realtime scheduling with CONFIG_RT_GROUP_SCHED=y

2017-07-06 Thread Lars Kellogg-Stedman
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"), but I don't have control over the kernel configuration. On this system, it

Re: [systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Mikhail Kasimov
06.07.2017 17:18, Michael Chapman пишет: > On Thu, 6 Jul 2017, Mikhail Kasimov wrote: >> Hello! >> >> 've got an interesting trouble on timer-activated service -- 'systemctl >> status' returns a log with 'Activating (start)' status: >> >> [1] >> == >> k_mikhail@linux-mk500:~> systemctl

Re: [systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Mikhail Kasimov
06.07.2017 18:27, Michael Chapman пишет: > On Fri, 7 Jul 2017, Mikhail Kasimov wrote: >> 06.07.2017 17:18, Michael Chapman пишет: >>> On Thu, 6 Jul 2017, Mikhail Kasimov wrote: Hello! 've got an interesting trouble on timer-activated service -- 'systemctl status' returns

Re: [systemd-devel] Timeout for 'Activating (start)' status

2017-07-06 Thread Mikhail Kasimov
06.07.2017 19:12, Mikhail Kasimov пишет: > > 06.07.2017 18:27, Michael Chapman пишет: >> On Fri, 7 Jul 2017, Mikhail Kasimov wrote: >>> 06.07.2017 17:18, Michael Chapman пишет: On Thu, 6 Jul 2017, Mikhail Kasimov wrote: > Hello! > > 've got an interesting trouble on