Re: [systemd-devel] systemd restart patch

2011-02-03 Thread Michael Biebl
2011/2/3 Tomasz Torcz : > On Thu, Feb 03, 2011 at 09:35:55PM +0100, Michael Biebl wrote: >> ExecStartOnFailure=/some/cmd (send an email or what not) > >  Isn't “OnFailure=send-email-to-admin.service” sufficent? Having to use a service file for this use case is imho cumbersome, especially since you

Re: [systemd-devel] systemd restart patch

2011-02-03 Thread Tomasz Torcz
On Thu, Feb 03, 2011 at 09:35:55PM +0100, Michael Biebl wrote: > 2011/2/3 Cristian Patrascu : > > So, for these last two features I created a patch, which adds two more > > options for a .service : > > - RestartRetries=n (where n is the number of restart retries) > > - ExecPostRestarts=/some/cmd (w

Re: [systemd-devel] Environment & EnvironmentFile in unit files

2011-02-03 Thread Lennart Poettering
On Thu, 27.01.11 11:31, Gustavo Sverzut Barbieri ([email protected]) wrote: > > However, I had my difficulties, and one of them is with environment > > variables in unit files. Are they really solely meant to be used for the > > started processes, and in no other unit file directives? I'd l

Re: [systemd-devel] Environment & EnvironmentFile in unit files

2011-02-03 Thread Lennart Poettering
On Thu, 27.01.11 11:10, Lucian Muresan ([email protected]) wrote: > cat /etc/systemd/system/lircd.service: > [Unit] > Description=LIRC Daemon > After=network.target > Name=lirc > > [Service] > Type=forking > EnvironmentFile=/etc/conf.d/lircd > PIDFile=/var/run/lirc/lircd.pid > ExecSta

Re: [systemd-devel] systemd restart patch

2011-02-03 Thread Michael Biebl
2011/2/3 Cristian Patrascu : > So, for these last two features I created a patch, which adds two more > options for a .service : > - RestartRetries=n (where n is the number of restart retries) > - ExecPostRestarts=/some/cmd (where the command "/some/cmd" will be executed > after restart retries are

Re: [systemd-devel] systemd --test starting with current state

2011-02-03 Thread Lennart Poettering
On Wed, 26.01.11 07:05, Andrey Borzenkov ([email protected]) wrote: > Currently systemd --test always starts from the "all off" state. This > makes it useless for debugging shutdown issues (which is not trivial > anyway). It would be extremely helpful to request unit transition > starting from t

Re: [systemd-devel] [[email protected]: [systemd-commits] src/pam-module.c]

2011-02-03 Thread Lennart Poettering
On Sat, 29.01.11 12:01, Andrey Borzenkov ([email protected]) wrote: > > On Fri, Dec 24, 2010 at 12:56 PM, Lennart Poettering > wrote: > > Heya, > > > > just wanted to let everybody know that I reverted the logic in > > pam_sytemd which automatically creates a cgroup in the 'cpu' hierarchy > > fo

Re: [systemd-devel] Multiple BusName's?

2011-02-03 Thread Lennart Poettering
On Sat, 29.01.11 11:38, Andrey Borzenkov ([email protected]) wrote: > Are multiple BusName possible? Real life example would be > wpa_supplicant that answers on two D-Bus service names from a single > binary. > > Semantic should likely be "and", as we assume in this case that binary > specified

Re: [systemd-devel] systemd as a session manager

2011-02-03 Thread Lennart Poettering
On Thu, 03.02.11 20:11, Peeters Simon ([email protected]) wrote: > hey, > > first of all, sorry if this doesn't belong on the devel-list, but i > couldn't find any other place to go with my question > > I am using systemd since v11 as init, but now i would like to also use > systemd as a s

[systemd-devel] systemd as a session manager

2011-02-03 Thread Peeters Simon
hey, first of all, sorry if this doesn't belong on the devel-list, but i couldn't find any other place to go with my question I am using systemd since v11 as init, but now i would like to also use systemd as a session manager (because gnome-session takes up more than half of my boot time), but i

[systemd-devel] systemd restart patch

2011-02-03 Thread Cristian Patrascu
In the company I work for, I must have/implement the following functionality of a systemd service: - when a service stops with an exit code not 0, that is when it fails, it must be restarted. This is implemented, by using the option *Restart=on-failure*. Eventually, also *RestartSec=* can be use