On Do, 27.09.18 14:22, prashantkumar dhotre (prashantkumardhotre@xxxxxxxxx) wrote: > 1) Is this a bug ? > 2) Why service is put to failed state on sigkill ? > 3) if putting service into failed state on sigkill is right thing to do , > they why dbus notification is not being sent in case of service that > supports restart. I am not sure I follow. But do note that if Restart= is turned on an configured properly, then systemd will transition the unit into "auto-restart" state instead of "failed". SIGKILL is not consiered a "clean" exit status by default. You can configure that with SuccessExitStatus= however. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: Failed state DBUS notification not received on sigkill of service
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Failed state DBUS notification not received on sigkill of service
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Date: Fri, 5 Oct 2018 19:36:52 +0200
- Cc: systemd-devel@xxxxxxxxxxxxxxx
- In-reply-to: <CA+VDgmPfWKxhM5Rg+DG3FEmPdA-TLBNQKSve2FXL6eYfRr98Dw@mail.gmail.com>
- References: <CA+VDgmPfWKxhM5Rg+DG3FEmPdA-TLBNQKSve2FXL6eYfRr98Dw@mail.gmail.com>
- References:
- Failed state DBUS notification not received on sigkill of service
- From: prashantkumar dhotre
- Failed state DBUS notification not received on sigkill of service
- Prev by Date: Re: systemd behavior during shutdown
- Next by Date: Re: Default on failure dependencies
- Previous by thread: Failed state DBUS notification not received on sigkill of service
- Next by thread: [PATCH v2] meson: use the host architecture compiler/linker for src/boot/efi
- Index(es):
 |