]> git.ipfire.org Git - thirdparty/systemd.git/commit
man: document that "systemd-run -M" propagates exit codes, and "machinectl shell... 4975/head
authorLennart Poettering <lennart@poettering.net>
Sat, 24 Dec 2016 00:08:15 +0000 (01:08 +0100)
committerLennart Poettering <lennart@poettering.net>
Tue, 27 Dec 2016 17:32:45 +0000 (18:32 +0100)
commit7f129a1f7c934123061aa26029cff1784805f878
tree08e64b18e474ded3f327c8dc877176ff2f063c0b
parent27e2e3231fc1edbbaa9f73be363900701ab4598d
man: document that "systemd-run -M" propagates exit codes, and "machinectl shell" does not

This adds a brief explanation, suggesting the use of "systemd-run -M" to
acquire exit status/code information for the invoked process.

My original plan was to propagate the exit code/status in "machinectl
shell" too, but this would mean we'd have to actively watch the shell's
runtime status, and thus would need full, highly privileged and
continious access to the container's system manager, the way
"systemd-run" does it. This would be quite a departure from the
simplistic, low-priviliged OpenShell() bus call implementation of the
current code, that really just acquires a PTY device with a shell
connected.

Moreover it would blur the lines between the two commands even further,
which I think is not desirable. Hence, from now on:

    "machinectl shell" is the full-session, interactive shell for human
    users

    "systemd-run -M …" is the low-level tool, that supports
    on-interactive mode, and is more configurable and suitable for
    streaming.

Fixes: #4215
man/machinectl.xml
man/systemd-run.xml