On Fri, 12.02.16 22:28, Mikhail Kasimov ([email protected]) wrote: > > TimeoutStopSec= is set to 90s by default. Because it is opt-out and > > not opt-in it's set pretty much in all cases. > > > > Note that when the RuntimeMaxSec= timeout hits and systemd starts > > terminating the service it does so by going through ExecStop= and > > ExecStopPost=. The TimeoutStopSec= timeout applies to each of them > > anyway. > > So, if systemd is going through ExecStop= and ExecStopPost= to stop unit > with RuntimeMaxSec=, which is the normal procedure to exit with > on-success exit-code, why systemd marks unit as "failed", when > RuntimeMaxSec= is hit? Can't catch the logic yet...
It's the same as with a daemon exiting non-zero. In that case we'll also continue with ExecStop= and place the service in a failed state. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
