Take the following structure:
A.service:
Requires=base.service
Type=fork
Restarts=no
B.service:
Requires=base.service
Type=fork
Restarts=no
After=A
C.service:
Requires=base.service
Type=fork
Restarts=no
After=B
Up.target:
Requires=A B C
Normally, systemctl start up.target brings up base, A,
-Original Message-
From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
Sent: Thursday, March 19, 2015 11:53 PM
To: Nekrasov, Alexander
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] StartLimitBurst prevents manual start-up of
a service
В Thu, 19 Mar 2015 15
-Original Message-
From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
Sent: Thursday, March 19, 2015 11:41 PM
To: Nekrasov, Alexander
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] not running ExecStop= when stopping
activating services?
В Thu, 19 Mar 2015
Hi,
There's a routine need to support this scenario: a service runs that can fail
and needs to be restarted.
But if it just keeps failing it doesn't make sense to keep restarting forever,
it's just overhead and the system is stuck. So in that case 1) the service
needs to be left stopped in
Totally missed those. Thanks. Will OnFailure= be activated when the limit is
hit? The manual only directly describes StartLimitAction= which isn’t exactly
what’s required
From: Mantas Mikulėnas [mailto:graw...@gmail.com]
Sent: Tuesday, December 09, 2014 1:05 PM
To: Nekrasov, Alexander
Cc
, Alexander; systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] reacting to unit failures (OnFailure)
On 12/02/2014 03:12 PM, Nekrasov, Alexander wrote:
Lennart just gave me a solution, thank you. I'll use templates
I have a system where components at the single node level have
, December 01, 2014 5:46 PM
To: Nekrasov, Alexander
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] reacting to unit failures (OnFailure)
On Mon, 01.12.14 17:10, Nekrasov, Alexander (alexander.nekra...@emc.com)
wrote:
Hello,
While converting from Upstart to SystemD, came
Hello,
While converting from Upstart to SystemD, came upon this issue. Is this case
not covered or am I missing something?
In Upstart, I can start a job when another job fails, and there's a $JOB
variable that tells me what was the job that failed.
start on (stopped RESULT=failed
