From: Lennart Poettering Date: Thu, 16 Feb 2023 15:30:09 +0000 (+0100) Subject: man: document new --exec switch for systemd-notify X-Git-Tag: v254-rc1~1251^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c4ef4df41728435dc3bf3c192281aa17fde2be3f;p=thirdparty%2Fsystemd.git man: document new --exec switch for systemd-notify --- diff --git a/man/systemd-notify.xml b/man/systemd-notify.xml index dd76cc0fb66..5a154686f5f 100644 --- a/man/systemd-notify.xml +++ b/man/systemd-notify.xml @@ -25,6 +25,9 @@ systemd-notify OPTIONS VARIABLE=VALUE + + systemd-notify --exec OPTIONS VARIABLE=VALUE ; CMDLINE + @@ -174,6 +177,20 @@ this option set is prone to race conditions in all other cases. + + + + If specified systemd-notify will execute another command line + after it completed its operation, replacing its own process. If used, the list of assignments to + include in the message sent must be followed by a ; character (as separate + argument), followed by the command line to execute. This permits "chaining" of commands, i.e. issuing + one operation, followed immediately by another, without changing PIDs. + + Note that many shells interpret ; as their own separator for command lines, + hence when systemd-notify is invoked from a shell the semicolon must usually be + escaped as \;. + +