Am 21.04.2012 13:47, schrieb Lennart Poettering: > On Wed, 18.04.12 13:54, Sven Anders ([email protected]) wrote: > >> Hello! >> >> Is it possible to act differently on exit codes? > > No. This is currently not possible. > >> The service may terminate fatal or temporarily. >> >> If the termination is temporarily (exit codes 0|12|13|14|15|16|17) I want the >> service to be respawned. On Exit codes 1|6|8|10|11|18|19 it should respawn, >> but >> with a longer sleep. >> Otherwise on the fatal case (exit codes 5|2|3|4|7|9) it should not try to >> respawn >> the service. > > This is a relatively complex restart logic. It probably is a better idea > to implement that as child process of systemd.
Hm, ok. It's just the "pppd" daemon I want to handle by systemd. I will check the alternatives. Regards Sven Anders -- Sven Anders <[email protected]> () UTF-8 Ribbon Campaign /\ Support plain text e-mail ANDURAS intranet security AG Messestrasse 3 - 94036 Passau - Germany Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55 Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
<<attachment: anders.vcf>>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
