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, B,
> -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
> "activa
> -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 servi
Hi All,
With these settings
[Service]
ExecStart=/cli run
ExecStop=/cli stop
Type=forking
PIDFile=/tmp/cli.pid
The service is active once "cli run" exits. A call to systemctl stop then
produces a call to "cli stop". This is as expected.
However if I call "systemctl stop" on this service before
Hi All,
Suppose I have a B.service that's doing important work, and an A.service that's
watching over B memory consumption. So I want to start A when I start B, and
stop A when I stop B. Also B, being important, should be allowed to restart on
failures. A, being just a monitor, should be left d
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
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 "fa
cember 02, 2014 10:28 AM
> To: Nekrasov, 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 te
devel-boun...@lists.freedesktop.org]
> On Behalf Of "Johann B. Gu?mundsson"
> Sent: Tuesday, December 02, 2014 9:55 AM
> To: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] reacting to unit failures (OnFailure)
>
>
> On 12/02/2014
t: Monday, 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,
>
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 PROCESS=post-
11 matches
Mail list logo
