Bug 38355 - Documentation about Exec* behavior on failure lacking
Summary: Documentation about Exec* behavior on failure lacking
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium minor
Assignee: Lennart Poettering
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-15 14:33 UTC by Ville Skyttä
Modified: 2013-03-20 02:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Ville Skyttä 2011-06-15 14:33:06 UTC
I find the man page documentation about behavior in cases where Exec* commands fail somewhat lacking.

The ExecStart doc kind of hints (in the part where "-" is discussed) what happens if a command line fails and there are multiple command lines, but it'd be good to be explicit about it: does a failure of one ExecStart command line cause the remaining ExecStart command lines to be skipped, or will they run anyway?

For ExecStartPre, ExecStartPost, ExecReload, ExecStop, and ExecStopPost the behavior when there are multiple command lines and one fails is not documented: are the remaining command lines for the same option executed or skipped?  Documenting it in ExecStartPre would be enough because the rest refer to ExecStartPre.

What happens if ExecStartPre fails is not documented - does it cause failure of service startup at that point without executing ExecStart, or does it simply pass through?
Comment 1 Zbigniew Jedrzejewski-Szmek 2013-03-20 02:19:16 UTC
Indeed the man page was lacking. Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=4c42e8.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.