On Wed, Feb 01, 2012 at 11:26:09PM +0100, Lennart Poettering wrote:
> On Wed, 01.02.12 20:11, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
>
> >
> > On Wed, Feb 01, 2012 at 07:42:16PM +0100, Lennart Poettering wrote:
> > > On Wed, 01.02.12 17:17, Michael Olbrich (m.olbr...@pengutronix.de) wr
I thought the DefaultDependencies=No was a given. Obviously that is what I
want.
On Thursday, February 02, 2012 04:39:09 Lennart Poettering wrote:
> On Wed, 01.02.12 18:51, Manuel Amador (rud...@rudd-o.com) wrote:
> > So:
> >
> > * Requires=ZFS.service in local-fs.target
> >
> > (accomplish
The reaping of generator processes run as part of a daemon-reload should not
call waitid(PID_ALL). The waitid() call in execute_directory() is intended only
to reap the executed processes, but if a service process exits at about the
same time as a daemon-reload, then that service process is reaped
On Thu, 02.02.12 17:32, Chris Paulson-Ellis (ch...@edesix.com) wrote:
> The reaping of generator processes run as part of a daemon-reload should not
> call waitid(PID_ALL). The waitid() call in execute_directory() is intended
> only
> to reap the executed processes, but if a service process exits
On Thu, 02.02.12 13:07, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > Hmm, so I think this should work differently. We already have a failure
> > logic for services, and if a service fails to send us WATCHDOG=1 in time
> > we should make use of that. That way, if service start up times out
On Thu, 02.02.12 19:42, Lennart Poettering (lenn...@poettering.net) wrote:
> a) track the watchdog alive messages (already merged)
>
> b) hook up the watchdog with the existing failure logic and introduce
> WatchdogSec for that.
>
> c) pass watchdog frequency to executed processes via env var
>
