Hi,
I see issue with OnFailure cfg
have a simple service which ignores sigterm and has OnFailure and Restart
cfg in its service file
issue restart of that service.
expectation is that OnFailure units will not be triggered (as per doc as
service is gonna restart even if it times out sigterm) but in
Am 2018-03-08 um 07:03 schrieb Andrei Borzenkov:
> 08.03.2018 02:37, Jakob Schürz пишет:
[...]
>
> This is apparently wrong, because service briefly goes via "failed"
> state every time it fails. It is true that if Restart= is set it
> immediately follows by "activating" state again, but OnFailu
08.03.2018 02:37, Jakob Schürz пишет:
> Hi there!
>
> I build a test-unit
>
> # cat [email protected]
> [Unit]
> Description=Testservice notification
> OnFailure=notification-telegram@%n.service
>
> [Service]
> Type=simple
> Restart=on-failure
> #RestartSec=2
> ExecStart=/bin/%i
> SyslogIdentifier=t
Hi there!
I build a test-unit
# cat [email protected]
[Unit]
Description=Testservice notification
OnFailure=notification-telegram@%n.service
[Service]
Type=simple
Restart=on-failure
#RestartSec=2
ExecStart=/bin/%i
SyslogIdentifier=test@%i.service
StartLimitBurst=5
StartLimitInterval=10
And the not
Hello all
A question about a slightly older version of systemd.
We are running systemd-37-25.fc16.x86_64.
We have a service called alarmist with a .service file like so:
[Unit]
Description=Raise alarms for %i
DefaultDependencies=no
[Service]
Type=oneshot
TimeoutSec=0
ExecStart=-/path/to/alarmi
