On Mon, 02.03.15 20:32, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote:
Why would you need this? Watchdog is to prevent system being stuck
somewhere. If activation fails within TimeoutStartSec=, systemd will
put the service in failed to activate state anyways.
Is waiting 20
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Wednesday, April 22, 2015 6:00 PM
To: Hoyer, Marko (ADITG/SW2)
Cc: Umut Tezduyar Lindskog; systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Service watchdog feature in state
ACTIVATING
On Wed, 22.04.15 17:59, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote:
So, I can see that having watchdog support during the activating phase
might make sense in this case, but I am not sure this case is strong
enough to add it to systemd proper, since it would complicate things
Hi Umut,
thx for answering
-Original Message-
From: Umut Tezduyar Lindskog [mailto:u...@tezduyar.com]
Sent: Monday, March 02, 2015 8:51 PM
To: Hoyer, Marko (ADITG/SW2)
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Service watchdog feature in state
ACTIVATING
Hi Marko,
On Sunday, March 1, 2015, Hoyer, Marko (ADITG/SW2) mho...@de.adit-jv.com
wrote:
Hi,
I ran into a use case where the activation phase of a service takes
significantly longer than the desired watchdog period (Activating:
10-20secs, Watchdog: 1-5secs).
I found out that the watchdog
Hi,
I ran into a use case where the activation phase of a service takes
significantly longer than the desired watchdog period (Activating: 10-20secs,
Watchdog: 1-5secs).
I found out that the watchdog features starts not before the service is in
state START_POST. This means for my use case
