diff options
Diffstat (limited to '')
-rw-r--r-- | man/systemd.service.xml | 8 | ||||
-rw-r--r-- | man/systemd.unit.xml | 2 |
2 files changed, 8 insertions, 2 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 17e446e203..02eb706789 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -423,6 +423,9 @@ <varname>ExecStart=</varname>, or <varname>ExecStartPost=</varname> fail (and are not prefixed with <literal>-</literal>, see above) or time out before the service is fully up, execution continues with commands specified in <varname>ExecStopPost=</varname>, the commands in <varname>ExecStop=</varname> are skipped.</para> + + <para>Note that the execution of <varname>ExecStartPost=</varname> is taken into account for the purpose of + <varname>Before=</varname>/<varname>After=</varname> ordering constraints.</para> </listitem> </varlistentry> @@ -534,7 +537,10 @@ service, as well as the main process' exit code and status, set in the <varname>$SERVICE_RESULT</varname>, <varname>$EXIT_CODE</varname> and <varname>$EXIT_STATUS</varname> environment variables, see <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for - details.</para></listitem> + details.</para> + + <para>Note that the execution of <varname>ExecStopPost=</varname> is taken into account for the purpose of + <varname>Before=</varname>/<varname>After=</varname> ordering constraints.</para></listitem> </varlistentry> <varlistentry> diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 64240208c2..0d223d74db 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -750,7 +750,7 @@ type when precisely a unit has finished starting up. Most importantly, for service units start-up is considered completed for the purpose of <varname>Before=</varname>/<varname>After=</varname> when all its configured start-up commands have been invoked and they either failed or reported start-up - success.</para> + success. Note that this does includes ExecStartPost (or ExecStopPost for the shutdown case).</para> <para>Note that those settings are independent of and orthogonal to the requirement dependencies as configured by <varname>Requires=</varname>, <varname>Wants=</varname>, <varname>Requisite=</varname>, |