table of contents
SYSTEMD-RUN(1) | systemd-run | SYSTEMD-RUN(1) |
NAME¶
systemd-run - Run programs in transient scope or service or timer units
SYNOPSIS¶
systemd-run [OPTIONS...] COMMAND [ARGS...]
systemd-run [OPTIONS...] [TIMER OPTIONS...] {COMMAND} [ARGS...]
DESCRIPTION¶
systemd-run may be used to create and start a transient .service or a transient .timer or a .scope unit and run the specified COMMAND in it.
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 systemctl list-units like any other unit. It will run in a clean and detached execution environment. systemd-run will start the service asynchronously in the background and immediately return.
If a command is run with timer options, transient timer unit also be created with transient service unit. But the transient timer unit is only started immediately. The transient service unit will be started when the transient timer is elapsed. If --unit= is specified with timer options, the COMMAND can be omitted. In this case, systemd-run assumes service unit is already loaded and creates transient timer unit only. To successfully create timer unit, already loaded service unit should be specified with --unit=. This transient timer unit can activate the existing service unit like any other timer.
If a command is run as transient scope unit, it will be started directly by systemd-run 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.
OPTIONS¶
The following options are understood:
--scope
--unit=
--property=, -p
--description=
--slice=
--remain-after-exit
--send-sighup
--service-type=
--uid=, --gid=
--nice=
--setenv=
--pty, -t
--quiet, -q
--on-active=, --on-boot=, --on-startup=, --on-unit-active=, --on-unit-inactive=
--on-calendar=
--timer-property=
-G, --collect
--system
-H, --host=
-M, --machine=
-h, --help
--version
All command line arguments after the first non-option argument become part of the command line of the launched process. If a command is run as service unit, its first argument needs to be an absolute binary path.
EXIT STATUS¶
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLES¶
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[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 Sep 08 07:37:21 bupkis env[19948]: BOOT_IMAGE=/vmlinuz-3.11.0-0.rc5.git6.2.fc20.x86_64
The following command invokes the updatedb(8) tool, but lowers the block IO weight for it to 10. See systemd.resource-control(5) for more information on the BlockIOWeight= property.
# systemd-run -p BlockIOWeight=10 updatedb
The following command will touch a file after 30 seconds.
# date; systemd-run --on-active=30 --timer-property=AccuracySec=100ms /bin/touch /tmp/foo Mon Dec 8 20:44:24 KST 2014 Running as unit run-71.timer. Will run as unit run-71.service. # journalctl -b -u run-73.timer -- Logs begin at Fri 2014-12-05 19:09:21 KST, end at Mon 2014-12-08 20:44:54 KST. -- 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. # journalctl -b -u run-73.service -- Logs begin at Fri 2014-12-05 19:09:21 KST, end at Mon 2014-12-08 20:44:54 KST. -- 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.
The following command invokes /bin/bash as a service passing its standard input, output and error to the calling TTY.
# systemd-run -t /bin/bash
SEE ALSO¶
systemd(1), systemctl(1), systemd.unit(5), systemd.service(5), systemd.scope(5), systemd.slice(5), systemd.exec(5), systemd.resource-control(5), systemd.timer(5), machinectl(1)
systemd 219 |