summaryrefslogtreecommitdiffstats
path: root/upstream/archlinux/man1/systemd-run.1
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/archlinux/man1/systemd-run.1')
-rw-r--r--upstream/archlinux/man1/systemd-run.124
1 files changed, 20 insertions, 4 deletions
diff --git a/upstream/archlinux/man1/systemd-run.1 b/upstream/archlinux/man1/systemd-run.1
index b2792c09..1d9c9c86 100644
--- a/upstream/archlinux/man1/systemd-run.1
+++ b/upstream/archlinux/man1/systemd-run.1
@@ -52,9 +52,10 @@ If a command is run as transient service unit, it will be started and managed by
like any other unit\&. It will run in a clean and detached execution environment, with the service manager as its parent process\&. In this mode,
\fBsystemd\-run\fR
will start the service asynchronously in the background and return after the command has begun execution (unless
-\fB\-\-no\-block\fR
-or
-\fB\-\-wait\fR
+\fB\-\-no\-block\fR,
+\fB\-\-wait\fR,
+\fB\-\-pipe\fR, or
+\fB\-\-pty\fR
are specified, see below)\&.
.PP
If a command is run as transient scope unit, it will be executed by
@@ -313,6 +314,14 @@ When invoking the command, the transient service connects its standard input, ou
\fBsystemd\-run\fR
is invoked on, via a pseudo TTY device\&. This allows running programs that expect interactive user input/output as services, such as interactive command shells\&.
.sp
+This option will result in
+\fBsystemd\-run\fR
+synchronously waiting for the transient service to terminate, similar to specifying
+\fB\-\-wait\fR\&. If specified along with
+\fB\-\-wait\fR,
+\fBsystemd\-run\fR
+won\*(Aqt exit when manually disconnecting from the pseudo TTY device\&.
+.sp
Note that
\fBmachinectl\fR(1)\*(Aqs
\fBshell\fR
@@ -330,7 +339,9 @@ If specified, standard input, output, and error of the transient service are inh
\fBsystemd\-run\fR
command itself\&. This allows
\fBsystemd\-run\fR
-to be used within shell pipelines\&. Note that this mode is not suitable for interactive command shells and similar, as the service process will not become a TTY controller when invoked on a terminal\&. Use
+to be used within shell pipelines\&.
+.sp
+Note that this mode is not suitable for interactive command shells and similar, as the service process will not become a TTY controller when invoked on a terminal\&. Use
\fB\-\-pty\fR
instead in that case\&.
.sp
@@ -343,6 +354,11 @@ are used in combination the more appropriate option is automatically determined
is used, and otherwise
\fB\-\-pipe\fR\&.
.sp
+This option will result in
+\fBsystemd\-run\fR
+synchronously waiting for the transient service to terminate, similar to specifying
+\fB\-\-wait\fR\&.
+.sp
When this option is used the original file descriptors
\fBsystemd\-run\fR
receives are passed to the service processes as\-is\&. If the service runs with different privileges than