Re: [systemd-devel] systemd shutdown query

On 10/06/2015 06:36 PM, Lennart Poettering wrote: On Mon, 05.10.15 15:49, Dushyant Uge (dushyan...@gmail.com) wrote: Hello there, I have two queries Some processes terminated immediately after writing reboot before reaching systemd unit ExecStop I am not sure I parse this, but when

Re: [systemd-devel] run no more than one of foo@.service at a time

> On Oct 6, 2015, at 6:19, Lennart Poettering wrote: > > On Mon, 05.10.15 09:04, Johannes Ernst (johannes.er...@gmail.com) wrote: > >> I have a foo@.service. When started as >> systemctl start foo@abc >> I’d like all other currently active foo@… services to stop,

Re: [systemd-devel] First steps with sd-bus

On Mon, 05.10.15 14:24, Iñigo Martínez (inigomarti...@gmail.com) wrote: > I was missing the XML policy file. After creating one, it worked > flawlessly. Thank you very much Daniel, > > One more question, I have been looking at systemd public man pages[0] > as the sd-bus API reference, but I

Re: [systemd-devel] systemd shutdown query

On Mon, 05.10.15 15:49, Dushyant Uge (dushyan...@gmail.com) wrote: > Hello there, > > I have two queries > > Some processes terminated immediately after writing reboot before reaching > systemd unit ExecStop I am not sure I parse this, but when services are shut down systemd won't kill their

Re: [systemd-devel] run no more than one of foo@.service at a time

Johannes Ernst wrote on 05/10/15 23:53: > >> On Oct 5, 2015, at 14:29, David Timothy Strauss >> > wrote: >> >> If you only want one instance running, why not just create one service >> and reconfigure/restart it? >> > Because the service

Re: [systemd-devel] run no more than one of foo@.service at a time

On Mon, 05.10.15 09:04, Johannes Ernst (johannes.er...@gmail.com) wrote: > I have a foo@.service. When started as > systemctl start foo@abc > I’d like all other currently active foo@… services to stop, and vice versa. > All of the foo@.services are supposed to be mutually exclusive with