From 36e257875379fb6d3c9733815b3b2189a76026f0 Mon Sep 17 00:00:00 2001 From: cyqsimon <28627918+cyqsimon@users.noreply.github.com> Date: Tue, 21 Mar 2023 11:19:40 +0800 Subject: [PATCH] systemd-run: add page (#9949) * systemd-run: add page * systemd-run: fix minor typo * systemd-run: reorder wording to reduce ambiguity * systemd-run: apply review suggestions Co-authored-by: K.B.Dharun Krishna --------- Co-authored-by: K.B.Dharun Krishna --- pages/linux/systemd-run.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 pages/linux/systemd-run.md diff --git a/pages/linux/systemd-run.md b/pages/linux/systemd-run.md new file mode 100644 index 0000000000..b74f7985e1 --- /dev/null +++ b/pages/linux/systemd-run.md @@ -0,0 +1,24 @@ +# systemd-run + +> Run programs in transient units. +> More information: . + +- Start a transient service: + +`sudo systemd-run {{command}} {{argument1 argument2 ...}}` + +- Start a transient service under the service manager of the current user (no privileges): + +`systemd-run --user {{command}} {{argument1 argument2 ...}}` + +- Start a transient service with a custom unit name and description: + +`sudo systemd-run --unit={{name}} --description={{string}} {{command}} {{argument1 argument2 ...}}` + +- Start a transient service that does not get cleaned up after it terminates with a custom environment variable: + +`sudo systemd-run --remain-after-exit --set-env={{name}}={{value}} {{command}} {{argument1 argument2 ...}}` + +- Start a transient timer that periodically runs its transient service (see `man systemd.time` for calendar event format): + +`sudo systemd-run --on-calendar={{calendar_event}} {{command}} {{argument1 argument2 ...}}`