From: Lennart Poettering Date: Tue, 7 Jan 2020 10:56:06 +0000 (+0100) Subject: man: document that scope units can fail, but not due to process exit statusses X-Git-Tag: v245-rc1~129^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f2e5e70410aba12aed9ac5184900218c3ae33a34;p=thirdparty%2Fsystemd.git man: document that scope units can fail, but not due to process exit statusses Let's clarify that scope units can fail, but not due to process exit statusses. This hopefully clears up some confusion that manifested in #14142: scope units can fail, but for other reasons than assumed there. Fixes: #14142 --- diff --git a/man/systemd.scope.xml b/man/systemd.scope.xml index daf3554db2b..e4de2b0fd0d 100644 --- a/man/systemd.scope.xml +++ b/man/systemd.scope.xml @@ -45,6 +45,15 @@ url="https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/">New Control Group Interfaces for an introduction on how to make use of scope units from programs. + + Note that unlike service units scope units have no "main" process, all processes in the scope are + equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process but + to the existance of any processes in the scope. This also means that the exit status of these processes + do not cause the scope unit to enter a failure state. Scope units may still enter a failure state, for + example due to resource exhaustion or stop timeouts being reached, but not due to programs inside of them + terminating uncleanly. Since processes managed as scope units generally remain children of the original + process that forked them off it's also the job of that process to collect their exit statuses and act on + them as needed.