Section: systemd-run (1)
Return to Main Contents
systemd-run - Run programs in transient scope or service units
systemd-run [OPTIONS...] COMMAND [ARGS...]
may be used to create and start a transient
unit and run the specified
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 show up in the output of
like any other unit. It will run in a clean and detached execution environment.
will start the service asynchronously in the background and immediately return.
If a command is run as transient scope unit, it will be started directly by
and thus inherit the execution environment of the caller. It is however managed by the service manager similar to normal services, and will also show up in the output of
systemctl list-units. Execution in this case is synchronous, and execution will return only when the command finishes.
The following options are understood:
Create a transient
unit instead of the default transient
Use this unit name instead of an automatically generated one.
Sets a unit property for the scope or service unit that is created. This takes an assignment in the same format as
Provide a description for the service or scope unit. If not specified, the command itself will be used as a description. See
Make the new
unit part of the specified slice, instead of the
After the service or scope 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
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
Sets the service type. Also see
systemd.service(5). This option has no effect in conjunction with
--scope. Defaults to
Runs the service process under the UNIX user and group. Also see
Runs the service process with the specified nice level. Also see
Runs the service process with the specified environment variables set. Also see
Talk to the service manager of the calling user, rather than the service manager of the system.
Talk to the service manager of the system. This is the implied default.
Execute the operation remotely. Specify a hostname, or a username and hostname separated by
"@", to connect to. The hostname may optionally be suffixed by a container name, separated by
":", which connects directly to a specific container on the specified host. This will use SSH to talk to the remote machine manager instance. Container names may be enumerated with
machinectl -H HOST.
Execute operation on a local container. Specify a container name to connect to.
Print a short help text and exit.
Print a short version string and exit.
All command-line arguments after the first non-option argument become part of the commandline of the launched process. If a command is run as service unit, its first argument needs to be an absolute binary path.
On success, 0 is returned, a non-zero failure code otherwise.
The following command will log the environment variables provided by systemd to services:
# systemd-run env
Running as unit run-19945.service.
# journalctl -u run-19945.service
Sep 08 07:37:21 bupkis systemd: Starting /usr/bin/env...
Sep 08 07:37:21 bupkis systemd: Started /usr/bin/env.
Sep 08 07:37:21 bupkis env: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Sep 08 07:37:21 bupkis env: LANG=en_US.UTF-8
Sep 08 07:37:21 bupkis env: BOOT_IMAGE=/vmlinuz-3.11.0-0.rc5.git6.2.fc20.x86_64
The following command invokes the
tool, but lowers the block IO weight for it to 10. See
for more information on the
# systemd-run -p BlockIOWeight=10 updatedb
- EXIT STATUS
- SEE ALSO