[systemd-devel] [PATCH] man: Document the actual behaviour of ExecStopPost
Mathieu Bridon
bochecha at fedoraproject.org
Fri Mar 8 06:17:33 PST 2013
On Friday, March 08, 2013 09:40 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Mar 08, 2013 at 04:26:36AM -0500, Mathieu Bridon wrote:
>> The documentation makes it sound like ExecStopPost is only run when
>> stopping the service with `systemctl stop foo.service`
>>
>> However, that is not the case, as it also gets run when the service
>> unexpectedly exists, crashes, or gets SIGKILLed.
>> ---
>> man/systemd.service.xml | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/man/systemd.service.xml b/man/systemd.service.xml
>> index 8977873..8001d73 100644
>> --- a/man/systemd.service.xml
>> +++ b/man/systemd.service.xml
>> @@ -464,8 +464,8 @@
>> <term><varname>ExecStopPost=</varname></term>
>> <listitem><para>Additional commands
>> that are executed after the service
>> - was stopped using the commands
>> - configured in
>> + was stopped, either unexpectedly or
>> + using the commands configured in
> Your patch goes in the right direction, but those are not exhaustive
> alternatives, e.g. I can stop the service using DBus.
But doesn't that end up « using the commands configured in ExecStop » ?
--
Mathieu
More information about the systemd-devel
mailing list