Section: systemd-run (1)
:systemd-run [OPTIONS...] COMMAND [ARGS...]
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 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.
The following options are understood:
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.
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
# systemd-run -p BlockIOWeight=10 updatedb
Tutoriais de Tecnologia Web