2018-07-03 00:15:39 +03:00
<?xml version='1.0'?>
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2013-07-10 09:24:46 +04:00
2014-02-13 23:33:51 +04:00
<refentry id= "systemd-run"
xmlns:xi="http://www.w3.org/2001/XInclude">
2013-07-10 09:24:46 +04:00
<refentryinfo >
<title > systemd-run</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-run</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-run</refname>
2017-12-18 18:07:11 +03:00
<refpurpose > Run programs in transient scope units, service units, or path-, socket-, or timer-triggered service units</refpurpose>
2013-07-10 09:24:46 +04:00
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
<command > systemd-run</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "plain" > <replaceable > COMMAND</replaceable>
<arg choice= "opt" rep= "repeat" > ARGS</arg>
</arg>
</cmdsynopsis>
2017-12-18 18:07:11 +03:00
<cmdsynopsis >
<command > systemd-run</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "opt" rep= "repeat" > PATH OPTIONS</arg>
<arg choice= "req" > <replaceable > COMMAND</replaceable> </arg>
<arg choice= "opt" rep= "repeat" > ARGS</arg>
</cmdsynopsis>
<cmdsynopsis >
<command > systemd-run</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "opt" rep= "repeat" > SOCKET OPTIONS</arg>
<arg choice= "req" > <replaceable > COMMAND</replaceable> </arg>
<arg choice= "opt" rep= "repeat" > ARGS</arg>
</cmdsynopsis>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
<cmdsynopsis >
<command > systemd-run</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "opt" rep= "repeat" > TIMER OPTIONS</arg>
<arg choice= "req" > <replaceable > COMMAND</replaceable> </arg>
<arg choice= "opt" rep= "repeat" > ARGS</arg>
</cmdsynopsis>
2013-07-10 09:24:46 +04:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2016-08-18 22:53:38 +03:00
<para > <command > systemd-run</command> may be used to create and start a transient <filename > .service</filename> or
<filename > .scope</filename> unit and run the specified <replaceable > COMMAND</replaceable> in it. It may also be
2017-12-18 18:07:11 +03:00
used to create and start a transient <filename > .path</filename> , <filename > .socket</filename> , or
<filename > .timer</filename> unit, that activates a <filename > .service</filename> unit when elapsing.</para>
2016-08-18 22:53:38 +03:00
<para > If a command is run as transient service unit, it will be started and managed by the service manager like any
other service, and thus shows up in the output of <command > systemctl list-units</command> 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, <command > systemd-run</command> will start the service asynchronously in the background and return after the
2017-01-20 03:10:30 +03:00
command has begun execution (unless <option > --no-block</option> or <option > --wait</option> are specified, see
2016-08-18 22:53:38 +03:00
below).</para>
2022-08-23 13:12:28 +03:00
<para > If a command is run as transient scope unit, it will be executed by <command > systemd-run</command>
itself as parent process and will thus inherit the execution environment of the caller. However, the
processes of the command are managed by the service manager similarly to normal services, and will show
up in the output of <command > systemctl list-units</command> . Execution in this case is synchronous, and
will return only when the command finishes. This mode is enabled via the <option > --scope</option> switch
2022-08-22 14:37:13 +03:00
(see below).</para>
2016-08-18 22:53:38 +03:00
2017-12-18 18:07:11 +03:00
<para > If a command is run with path, socket, or timer options such as <option > --on-calendar=</option> (see below),
a transient path, socket, or timer unit is created alongside the service unit for the specified command. Only the
transient path, socket, or timer unit is started immediately, the transient service unit will be triggered by the
path, socket, or timer unit. If the <option > --unit=</option> option is specified, the
<replaceable > COMMAND</replaceable> may be omitted. In this case, <command > systemd-run</command> creates only a
<filename > .path</filename> , <filename > .socket</filename> , or <filename > .timer</filename> unit that triggers the
specified unit.</para>
2018-07-17 13:01:26 +03:00
2022-08-22 14:37:13 +03:00
<para > By default, services created with <command > systemd-run</command> default to the
<option > simple</option> type, see the description of <varname > Type=</varname> in
2018-07-17 13:01:26 +03:00
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
2022-08-22 14:37:13 +03:00
details. Note that when this type is used, the service manager (and thus the
<command > systemd-run</command> command) considers service start-up successful as soon as the
<function > fork()</function> for the main service process succeeded, i.e. before the
<function > execve()</function> is invoked, and thus even if the specified command cannot be started.
Consider using the <option > exec</option> service type (i.e. <option > --property=Type=exec</option> ) to
ensure that <command > systemd-run</command> returns successfully only if the specified command line has
been successfully started.</para>
2013-07-10 09:24:46 +04:00
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
2015-09-01 19:43:08 +03:00
<varlistentry >
<term > <option > --no-ask-password</option> </term>
<listitem > <para > Do not query the user for authentication for
privileged operations.</para> </listitem>
</varlistentry>
2013-07-10 09:24:46 +04:00
<varlistentry >
<term > <option > --scope</option> </term>
<listitem >
2016-08-18 22:53:38 +03:00
<para > Create a transient <filename > .scope</filename> unit instead of the default transient
<filename > .service</filename> unit (see above).
2013-07-10 09:24:46 +04:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --unit=</option> </term>
2019-10-23 10:13:15 +03:00
<term > <option > -u</option> </term>
2013-07-10 09:24:46 +04:00
<listitem > <para > Use this unit name instead of an automatically
generated one.</para> </listitem>
</varlistentry>
2014-03-05 06:36:22 +04:00
<varlistentry >
<term > <option > --property=</option> </term>
<term > <option > -p</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > Sets a property on the scope or service unit that is created. This option takes an assignment
in the same format as
2014-03-05 06:36:22 +04:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> 's
<command > set-property</command> command.</para>
</listitem>
</varlistentry>
2013-07-10 09:24:46 +04:00
<varlistentry >
<term > <option > --description=</option> </term>
2017-12-18 18:07:11 +03:00
<listitem > <para > Provide a description for the service, scope, path, socket, or timer unit. If not specified,
the command itself will be used as a description. See <varname > Description=</varname> in
2013-07-10 09:24:46 +04:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --slice=</option> </term>
2020-04-08 19:45:31 +03:00
<listitem > <para > Make the new <filename > .service</filename> or <filename > .scope</filename> unit part
of the specified slice, instead of <filename > system.slice</filename> (when running in
<option > --system</option> mode) or the root slice (when running in <option > --user</option>
mode).</para>
2013-07-10 09:24:46 +04:00
</listitem>
</varlistentry>
2013-07-26 18:09:25 +04:00
2020-04-08 15:57:52 +03:00
<varlistentry >
<term > <option > --slice-inherit</option> </term>
<listitem > <para > Make the new <filename > .service</filename> or <filename > .scope</filename> unit part
of the inherited slice. This option can be combined with <option > --slice=</option> .</para>
<para > An inherited slice is located within <command > systemd-run</command> slice. Example: if
<command > systemd-run</command> slice is <filename > foo.slice</filename> , and the
<option > --slice=</option> argument is <filename > bar</filename> , the unit will be placed under the
<filename > foo-bar.slice</filename> .</para>
</listitem>
</varlistentry>
2013-07-26 18:09:25 +04:00
<varlistentry >
2018-01-10 16:55:23 +03:00
<term > <option > -r</option> </term>
2013-07-26 18:09:25 +04:00
<term > <option > --remain-after-exit</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > After the service process has terminated, keep the service around until it is explicitly
stopped. This is useful to collect runtime information about the service after it finished running. Also see
2013-07-26 18:09:25 +04:00
<varname > RemainAfterExit=</varname> in
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
</listitem>
</varlistentry>
2013-07-30 04:28:22 +04:00
<varlistentry >
<term > <option > --send-sighup</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > When terminating the scope or service unit, send a SIGHUP immediately after SIGTERM. This is
useful to indicate to shells and shell-like processes that the connection has been severed. Also see
2014-03-05 06:37:48 +04:00
<varname > SendSIGHUP=</varname> in
2013-07-30 04:28:22 +04:00
<citerefentry > <refentrytitle > systemd.kill</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
</listitem>
</varlistentry>
2014-02-13 23:33:51 +04:00
2014-03-05 06:37:48 +04:00
<varlistentry >
<term > <option > --service-type=</option> </term>
<listitem > <para > Sets the service type. Also see
<varname > Type=</varname> in
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> . This
option has no effect in conjunction with
<option > --scope</option> . Defaults to
<constant > simple</constant> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --uid=</option> </term>
<term > <option > --gid=</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > Runs the service process under the specified UNIX user and group. Also see
<varname > User=</varname> and <varname > Group=</varname> in
2014-03-05 21:57:21 +04:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
2014-03-05 06:37:48 +04:00
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --nice=</option> </term>
<listitem > <para > Runs the service process with the specified
nice level. Also see <varname > Nice=</varname> in
2014-03-05 21:57:21 +04:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
2014-03-05 06:37:48 +04:00
</listitem>
2018-11-22 14:07:25 +03:00
</varlistentry>
<varlistentry >
<term > <option > --working-directory=</option> </term>
<listitem > <para > Runs the service process with the specified working directory. Also see
<varname > WorkingDirectory=</varname> in
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --same-dir</option> </term>
<term > <option > -d</option> </term>
2022-08-23 13:12:28 +03:00
<listitem > <para > Similar to <option > --working-directory=</option> , but uses the current working
directory of the caller for the service to execute.</para> </listitem>
2014-03-05 06:37:48 +04:00
</varlistentry>
<varlistentry >
2021-08-10 18:25:47 +03:00
<term > <option > -E <replaceable > NAME</replaceable> [=<replaceable > VALUE</replaceable> ]</option> </term>
<term > <option > --setenv=<replaceable > NAME</replaceable> [=<replaceable > VALUE</replaceable> ]</option> </term>
2014-03-05 06:37:48 +04:00
2021-08-10 18:25:47 +03:00
<listitem > <para > Runs the service process with the specified environment variable set. This parameter
may be used more than once to set multiple variables. When <literal > =</literal> and
<replaceable > VALUE</replaceable> are omitted, the value of the variable with the same name in the
program environment will be used.</para>
<para > Also see <varname > Environment=</varname> in
2014-03-05 21:57:21 +04:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
2014-03-05 06:37:48 +04:00
</listitem>
</varlistentry>
2014-12-22 21:45:32 +03:00
<varlistentry >
<term > <option > --pty</option> </term>
<term > <option > -t</option> </term>
2017-09-08 16:38:40 +03:00
<listitem > <para > When invoking the command, the transient service connects its standard input, output and error
to the terminal <command > systemd-run</command> is invoked on, via a pseudo TTY device. This allows running
2017-09-13 23:11:03 +03:00
programs that expect interactive user input/output as services, such as interactive command shells.</para>
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
2016-12-24 03:08:15 +03:00
<para > Note that
<citerefentry > <refentrytitle > machinectl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> 's
<command > shell</command> command is usually a better alternative for requesting a new, interactive login
2017-09-08 16:38:40 +03:00
session on the local host or a local container.</para>
<para > See below for details on how this switch combines with <option > --pipe</option> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --pipe</option> </term>
<term > <option > -P</option> </term>
<listitem > <para > If specified, standard input, output, and error of the transient service are inherited from the
2017-09-13 23:11:03 +03:00
<command > systemd-run</command> command itself. This allows <command > systemd-run</command>
to be used within shell pipelines.
Note that this mode is not suitable for interactive command shells and similar, as the
2017-09-14 11:23:36 +03:00
service process will not become a TTY controller when invoked on a terminal. Use <option > --pty</option> instead
2017-09-08 16:38:40 +03:00
in that case.</para>
<para > When both <option > --pipe</option> and <option > --pty</option> are used in combination the more appropriate
option is automatically determined and used. Specifically, when invoked with standard input, output and error
2017-11-14 12:51:09 +03:00
connected to a TTY <option > --pty</option> is used, and otherwise <option > --pipe</option> .</para>
<para > When this option is used the original file descriptors <command > systemd-run</command> receives are passed
to the service processes as-is. If the service runs with different privileges than
<command > systemd-run</command> , this means the service might not be able to re-open the passed file
descriptors, due to normal file descriptor access restrictions. If the invoked process is a shell script that
uses the <command > echo "hello" > /dev/stderr</command> construct for writing messages to stderr, this might
cause problems, as this only works if stderr can be re-opened. To mitigate this use the construct <command > echo
"hello" >& 2</command> instead, which is mostly equivalent and avoids this pitfall.</para> </listitem>
2014-12-22 21:45:32 +03:00
</varlistentry>
2014-02-13 23:40:40 +04:00
2018-11-22 21:24:48 +03:00
<varlistentry >
<term > <option > --shell</option> </term>
<term > <option > -S</option> </term>
<listitem > <para > A shortcut for <literal > --pty --same-dir --wait --collect --service-type=exec $SHELL</literal> ,
i.e. requests an interactive shell in the current working directory, running in service context, accessible
with a single switch.</para> </listitem>
</varlistentry>
2014-12-22 22:39:10 +03:00
<varlistentry >
<term > <option > --quiet</option> </term>
<term > <option > -q</option> </term>
<listitem > <para > Suppresses additional informational output
while running. This is particularly useful in combination with
<option > --pty</option> when it will suppress the initial
message explaining how to terminate the TTY connection.</para> </listitem>
</varlistentry>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
<varlistentry >
<term > <option > --on-active=</option> </term>
<term > <option > --on-boot=</option> </term>
<term > <option > --on-startup=</option> </term>
<term > <option > --on-unit-active=</option> </term>
<term > <option > --on-unit-inactive=</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > Defines a monotonic timer relative to different starting points for starting the specified
command. See <varname > OnActiveSec=</varname> , <varname > OnBootSec=</varname> , <varname > OnStartupSec=</varname> ,
<varname > OnUnitActiveSec=</varname> and <varname > OnUnitInactiveSec=</varname> in
<citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
2017-12-18 18:07:11 +03:00
details. These options are shortcuts for <command > --timer-property=</command> with the relevant properties.
These options may not be combined with <option > --scope</option> or <option > --pty</option> .</para>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <option > --on-calendar=</option> </term>
2016-08-18 22:53:38 +03:00
<listitem > <para > Defines a calendar timer for starting the specified command. See <varname > OnCalendar=</varname>
in <citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> . This
2017-12-18 18:07:11 +03:00
option is a shortcut for <command > --timer-property=OnCalendar=</command> . This option may not be combined with
<option > --scope</option> or <option > --pty</option> .</para>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
</listitem>
</varlistentry>
2019-03-15 01:28:46 +03:00
<varlistentry >
<term > <option > --on-clock-change</option> </term>
<term > <option > --on-timezone-change</option> </term>
<listitem > <para > Defines a trigger based on system clock jumps or timezone changes for starting the
specified command. See <varname > OnClockChange=</varname> and <varname > OnTimezoneChange=</varname> in
<citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> . These
options are shortcuts for <command > --timer-property=OnClockChange=yes</command> and
<command > --timer-property=OnTimezoneChange=yes</command> . These options may not be combined with
<option > --scope</option> or <option > --pty</option> .</para> </listitem>
</varlistentry>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
<varlistentry >
2017-12-18 18:07:11 +03:00
<term > <option > --path-property=</option> </term>
<term > <option > --socket-property=</option> </term>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
<term > <option > --timer-property=</option> </term>
2022-08-23 13:12:28 +03:00
<listitem > <para > Sets a property on the path, socket, or timer unit that is created. This option is
similar to <option > --property=</option> , but applies to the transient path, socket, or timer unit
rather than the transient service unit created. This option takes an assignment in the same format as
2017-12-18 18:07:11 +03:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> 's
<command > set-property</command> command. These options may not be combined with
<option > --scope</option> or <option > --pty</option> .</para>
</listitem>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
</varlistentry>
2015-04-28 13:33:19 +03:00
<varlistentry >
<term > <option > --no-block</option> </term>
<listitem >
2016-08-18 22:53:38 +03:00
<para > Do not synchronously wait for the unit start operation to finish. If this option is not specified, the
start request for the transient unit will be verified, enqueued and <command > systemd-run</command> will wait
until the unit's start-up is completed. By passing this argument, it is only verified and enqueued. This
option may not be combined with <option > --wait</option> .</para>
2015-04-28 13:33:19 +03:00
</listitem>
</varlistentry>
2016-08-18 22:53:38 +03:00
<varlistentry >
<term > <option > --wait</option> </term>
<listitem > <para > Synchronously wait for the transient service to terminate. If this option is specified, the
start request for the transient unit is verified, enqueued, and waited for. Subsequently the invoked unit is
monitored, and it is waited until it is deactivated again (most likely because the specified command
completed). On exit, terse information about the unit's runtime is shown, including total runtime (as well as
CPU usage, if <option > --property=CPUAccounting=1</option> was set) and the exit code and status of the main
process. This output may be suppressed with <option > --quiet</option> . This option may not be combined with
2017-12-18 18:07:11 +03:00
<option > --no-block</option> , <option > --scope</option> or the various path, socket, or timer options.</para> </listitem>
2016-08-18 22:53:38 +03:00
</varlistentry>
2017-11-13 19:17:53 +03:00
<varlistentry >
<term > <option > -G</option> </term>
<term > <option > --collect</option> </term>
<listitem > <para > Unload the transient unit after it completed, even if it failed. Normally, without this option,
all units that ran and failed are kept in memory until the user explicitly resets their failure state with
<command > systemctl reset-failed</command> or an equivalent command. On the other hand, units that ran
successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more
aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for
<command > --property=CollectMode=inactive-or-failed</command> , see the explanation for
<varname > CollectMode=</varname> in
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for further
information.</para> </listitem>
</varlistentry>
2014-12-22 21:45:32 +03:00
<xi:include href= "user-system-options.xml" xpointer= "user" />
<xi:include href= "user-system-options.xml" xpointer= "system" />
<xi:include href= "user-system-options.xml" xpointer= "host" />
<xi:include href= "user-system-options.xml" xpointer= "machine" />
2014-02-13 23:33:51 +04:00
<xi:include href= "standard-options.xml" xpointer= "help" />
<xi:include href= "standard-options.xml" xpointer= "version" />
2013-07-10 09:24:46 +04:00
</variablelist>
2022-08-22 14:37:13 +03:00
<para > All command line arguments after the first non-option argument become part of the command line of
the launched process.</para>
2013-07-10 09:24:46 +04:00
</refsect1>
<refsect1 >
<title > Exit status</title>
2019-10-29 20:07:07 +03:00
<para > On success, 0 is returned. If <command > systemd-run</command> failed to start the service, a
non-zero return value will be returned. If <command > systemd-run</command> waits for the service to
terminate, the return value will be propagated from the service. 0 will be returned on success, including
all the cases where systemd considers a service to have exited cleanly, see the discussion of
<varname > SuccessExitStatus=</varname> in
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
2013-07-10 09:24:46 +04:00
</refsect1>
2013-09-08 15:51:39 +04:00
<refsect1 >
2014-03-05 06:36:22 +04:00
<title > Examples</title>
2013-09-08 15:51:39 +04:00
2016-04-09 22:41:04 +03:00
<example >
<title > Logging environment variables provided by systemd to services</title>
2013-09-08 15:51:39 +04:00
2016-04-09 22:41:04 +03:00
<programlisting > # systemd-run env
2016-04-04 12:28:14 +03:00
Running as unit: run-19945.service
2013-09-08 15:51:39 +04:00
# journalctl -u run-19945.service
Sep 08 07:37:21 bupkis systemd[1]: Starting /usr/bin/env...
Sep 08 07:37:21 bupkis systemd[1]: Started /usr/bin/env.
Sep 08 07:37:21 bupkis env[19948]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Sep 08 07:37:21 bupkis env[19948]: LANG=en_US.UTF-8
2014-02-14 18:56:19 +04:00
Sep 08 07:37:21 bupkis env[19948]: BOOT_IMAGE=/vmlinuz-3.11.0-0.rc5.git6.2.fc20.x86_64</programlisting>
2016-04-09 22:41:04 +03:00
</example>
2014-03-05 06:36:22 +04:00
2016-04-09 22:41:04 +03:00
<example >
<title > Limiting resources available to a command</title>
2014-03-05 06:36:22 +04:00
2022-07-21 12:19:13 +03:00
<programlisting > # systemd-run -p IOWeight=10 updatedb</programlisting>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
2022-07-21 12:19:13 +03:00
<para > This command invokes the <citerefentry
project='man-pages'><refentrytitle > updatedb</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2016-04-09 22:41:04 +03:00
tool, but lowers the block I/O weight for it to 10. See
<citerefentry > <refentrytitle > systemd.resource-control</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2022-07-21 12:19:13 +03:00
for more information on the <varname > IOWeight=</varname> property.</para>
2016-04-09 22:41:04 +03:00
</example>
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
2016-04-09 22:41:04 +03:00
<example >
<title > Running commands at a specified time</title>
<para > The following command will touch a file after 30 seconds.</para>
<programlisting > # date; systemd-run --on-active=30 --timer-property=AccuracySec=100ms /bin/touch /tmp/foo
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
Mon Dec 8 20:44:24 KST 2014
2016-04-04 12:28:14 +03:00
Running as unit: run-71.timer
Will run service as unit: run-71.service
2015-04-22 23:24:24 +03:00
# journalctl -b -u run-71.timer
2020-07-24 13:19:08 +03:00
-- Journal begins at Fri 2014-12-05 19:09:21 KST, ends at Mon 2014-12-08 20:44:54 KST. --
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
Dec 08 20:44:38 container systemd[1]: Starting /bin/touch /tmp/foo.
Dec 08 20:44:38 container systemd[1]: Started /bin/touch /tmp/foo.
2015-04-22 23:24:24 +03:00
# journalctl -b -u run-71.service
2020-07-24 13:19:08 +03:00
-- Journal begins at Fri 2014-12-05 19:09:21 KST, ends at Mon 2014-12-08 20:44:54 KST. --
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
Dec 08 20:44:48 container systemd[1]: Starting /bin/touch /tmp/foo...
Dec 08 20:44:48 container systemd[1]: Started /bin/touch /tmp/foo.</programlisting>
2016-04-09 22:41:04 +03:00
</example>
2014-12-22 21:45:32 +03:00
2016-04-09 22:41:04 +03:00
<example >
<title > Allowing access to the tty</title>
2014-12-22 21:45:32 +03:00
2022-04-12 12:02:16 +03:00
<para > The following command invokes <citerefentry project= 'die-net' > <refentrytitle > bash</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2021-12-12 22:30:26 +03:00
as a service passing its standard input, output and error to the calling TTY.</para>
2014-12-22 21:45:32 +03:00
2021-12-12 22:30:26 +03:00
<programlisting > # systemd-run -t --send-sighup bash</programlisting>
2016-04-09 22:41:04 +03:00
</example>
2016-04-09 23:22:08 +03:00
<example >
<title > Start <command > screen</command> as a user service</title>
<programlisting > $ systemd-run --scope --user screen
Running scope as unit run-r14b0047ab6df45bfb45e7786cc839e76.scope.
$ screen -ls
There is a screen on:
492..laptop (Detached)
1 Socket in /var/run/screen/S-fatima.
</programlisting>
<para > This starts the <command > screen</command> process as a child of the
<command > systemd --user</command> process that was started by
<filename > user@.service</filename> , in a scope unit. A
<citerefentry > <refentrytitle > systemd.scope</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
unit is used instead of a
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
unit, because <command > screen</command> will exit when detaching from the terminal,
and a service unit would be terminated. Running <command > screen</command>
as a user unit has the advantage that it is not part of the session scope.
If <varname > KillUserProcesses=yes</varname> is configured in
<citerefentry > <refentrytitle > logind.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
the default, the session scope will be terminated when the user logs
out of that session.</para>
<para > The <filename > user@.service</filename> is started automatically
when the user first logs in, and stays around as long as at least one
login session is open. After the user logs out of the last session,
<filename > user@.service</filename> and all services underneath it
2016-10-13 00:02:44 +03:00
are terminated. This behavior is the default, when "lingering" is
2016-04-09 23:22:08 +03:00
not enabled for that user. Enabling lingering means that
<filename > user@.service</filename> is started automatically during
boot, even if the user is not logged in, and that the service is
not terminated when the user logs out.</para>
<para > Enabling lingering allows the user to run processes without being logged in,
for example to allow <command > screen</command> to persist after the user logs out,
even if the session scope is terminated. In the default configuration, users can
enable lingering for themselves:</para>
<programlisting > $ loginctl enable-linger</programlisting>
</example>
2019-10-29 20:07:07 +03:00
<example >
<title > Return value</title>
<programlisting > $ systemd-run --user --wait true
$ systemd-run --user --wait -p SuccessExitStatus=11 bash -c 'exit 11'
$ systemd-run --user --wait -p SuccessExitStatus=SIGUSR1 bash -c 'kill -SIGUSR1 $$$$'</programlisting>
<para > Those three invocations will succeed, i.e. terminate with an exit code of 0.</para>
</example>
2013-09-08 15:51:39 +04:00
</refsect1>
2013-07-10 09:24:46 +04:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2013-07-19 19:51:26 +04:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2013-07-10 09:24:46 +04:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.scope</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-10-30 19:44:55 +04:00
<citerefentry > <refentrytitle > systemd.slice</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2014-03-05 06:36:22 +04:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.resource-control</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
run: introduce timer support option
Support timer options --on-active=, --on-boot=, --on-startup=,
--on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
OnUnitActiveSec=, OnUnitInactiveSec=, OnCalendar= of timer
respectively. And OnCalendar= and WakeSystem= supported by
--timer-property= option like --property= of systemd-run.
And if --unit= option and timer options are specified the command can
be omitted. In this case, systemd-run assumes the target service is
already loaded. And just try to generate transient timer unit only.
2014-12-09 10:07:16 +03:00
<citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2016-08-06 01:32:46 +03:00
<citerefentry > <refentrytitle > systemd-mount</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2013-10-30 19:44:55 +04:00
<citerefentry > <refentrytitle > machinectl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2013-07-10 09:24:46 +04:00
</para>
</refsect1>
</refentry>