Re: [systemd-devel] How to start a unit right after another unit terminates?

2018-07-16 Thread Andrei Borzenkov
16.07.2018 21:32, John Ioannidis пишет: > Assume I have a one-shot service, *phase1.service*, which runs for a while > and then terminates. I want to have a *phase2.service* start up when phase1 > terminates. > > I cannot change anything in phase1.service's systemd files or code or > anything, or

Re: [systemd-devel] How to start a unit right after another unit terminates?

2018-07-16 Thread Mantas Mikulėnas
On Mon, Jul 16, 2018, 21:33 John Ioannidis wrote: > Assume I have a one-shot service, *phase1.service*, which runs for a > while and then terminates. I want to have a *phase2.service* start up > when phase1 terminates. > > I cannot change anything in phase1.service's systemd files or code or > an

[systemd-devel] How to start a unit right after another unit terminates?

2018-07-16 Thread John Ioannidis
Assume I have a one-shot service, *phase1.service*, which runs for a while and then terminates. I want to have a *phase2.service* start up when phase1 terminates. I cannot change anything in phase1.service's systemd files or code or anything, or I would not be asking this question! A dirty workar

Re: [systemd-devel] Suggestion for a system fs change notify service.

2018-07-16 Thread Mantas Mikulėnas
On Mon, Jul 16, 2018 at 9:38 AM Stef Bon wrote: > Filsesystems like cifs and nfs are a problem. I think that they can > also contact the "systemd-fsnotify" daemon through a fd (like with > autofs) but I;ve not spent a lot of time to this issue. > SMB has change notifications – afaik the Linux cl

Re: [systemd-devel] Suggestion for a system fs change notify service.

2018-07-16 Thread Lennart Poettering
On Mo, 16.07.18 08:36, Stef Bon (stef...@gmail.com) wrote: > My idea is that a low level systemd-fsnotify which offers a socket to > fuse filesystems to handle the setting of watches is the best > sollution. And of course the processing of events when something is > reported by the fuse fs: this c

Re: [systemd-devel] logind: How to process enumerate buttons in parallel?

2018-07-16 Thread Lennart Poettering
On Mo, 16.07.18 10:25, Paul Menzel (pmenzel+systemd-de...@molgen.mpg.de) wrote: > Jul 16 08:22:54.312955 kodi systemd-logind[169]: Watching system buttons on > /dev/input/event1 (Power Button) > Jul 16 08:22:54.514965 kodi systemd-logind[169]: Watching system buttons on > /dev/input/event0 (Powe

Re: [systemd-devel] logind: How to process enumerate buttons in parallel?

2018-07-16 Thread Paul Menzel
Dear Lennart, Thank you for your response. On 07/13/18 17:12, Lennart Poettering wrote: > On Do, 12.07.18 16:51, Paul Menzel wrote: >> Trying to decrease the start-up time, I noticed that `systemd-logind` >> probes devices in serial(?) (instead of parallel). >> >> From `manager_enumerate_butto