summaryrefslogtreecommitdiffstats
path: root/man/systemd-run.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* run: expand variables also with --scopeZbigniew Jędrzejewski-Szmek2023-04-241-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes syntax be the same for commands which are started by the manager and those which are spawned directly (when --scope is used). Before: $ systemd-run -q -t echo '$TERM' xterm-256color $ systemd-run -q --scope echo '$TERM' $TERM Now: $ systemd-run -q --scope echo '$TERM' xterm-256color Previous behaviour can be restored via --expand-environment=no: $ systemd-run -q --scope --expand-environment=no echo '$TERM' $TERM Fixes #22948. At some level, this is a compat break. Fortunately --scope is not very widely used, so I think we can get away with this. Having different syntax depending on whether --scope was used or not was bad UX. A NEWS entry will be required.
* man/systemd-run: add examples explaining how variable expansion is performedZbigniew Jędrzejewski-Szmek2023-04-241-0/+36
|
* run: add --expand-environment=no to disable server-side envvar expansionZbigniew Jędrzejewski-Szmek2023-04-241-1/+25
| | | | | | | | | | This uses StartExecEx to get the equivalent of ExecStart=:. StartExecEx was added in b3d593673c5b8b0b7d781fd26ab2062ca6e7dbdb, so this will not work with older systemds. A hint is emitted if we get an error indicating lack of support. PID1 returns SD_BUS_ERROR_PROPERTY_READ_ONLY, but I'm checking for SD_BUS_ERROR_UNKNOWN_PROPERTY too for safety.
* test: drop whitespace after shell redirection operatorsZbigniew Jędrzejewski-Szmek2023-02-061-1/+1
| | | | | | | | | | (The one case that is left unchanged is '< <(subcommand)'.) This way, the style with no gap was already dominant. This way, the reader immediately knows that ' < ' is a comparison operator and ' << ' is a shift. In a few cases, replace custom EOF replacement by just EOF. There is no point in using someting like "_EOL" unless "EOF" appears in the text.
* man/systemd-run: Refer to man-pages project (man7.org) when citing bash(1)BerndAdameit2022-09-181-1/+1
|
* Merge pull request #24408 from keszybz/execstart-escapeLennart Poettering2022-08-251-13/+12
|\ | | | | Properly escape ExecStart= commandlines in transient units
| * man/run: we accept relative paths for runZbigniew Jędrzejewski-Szmek2022-08-241-13/+12
| | | | | | | | | | I think this is a left-over from before we changed ExecStart= to allow non-absolute paths, *and* changed systemd-run itself to resolve paths too.
* | Merge pull request #24072 from poettering/remove-cgroupsv1-docsLennart Poettering2022-08-241-5/+4
|\ \ | |/ |/| decgroupsv1ification: first steps – remove from docs, and generate warnings
| * docs: remove documentation about cgroupsv1 settingsLennart Poettering2022-08-231-5/+4
| | | | | | | | | | it's legacy. We'll continue to support it in code, but let's simplify the docs a bit, and not mention this legacy stuff anymore.
* | man: similar → similarlyZbigniew Jędrzejewski-Szmek2022-08-231-10/+11
|/ | | | | | | | | Something *is* similar Something *works* similarly Something does something, similarly to how something else does something See https://sites.ulethbridge.ca/roussel/2017/11/29/similar-and-similarly-are-they-similar/ for a clear explanation.
* Fix man page linksZbigniew Jędrzejewski-Szmek2022-04-121-1/+1
| | | | Based on linkchecker as usual.
* man/sd-run: /bin/bash -> bash in -t exampleнаб2021-12-121-3/+3
| | | | sd-run already does PATH lookup via find_executable_full()
* run: allow --setenv=FOOZbigniew Jędrzejewski-Szmek2021-08-111-4/+8
|
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* journal: adjust line about when the journal begins and endsZbigniew Jędrzejewski-Szmek2020-08-171-2/+2
| | | | | | | This comes up occasionally with new users. The phrase "Logs begin ..." is ambiguous because it can be taken to mean the logs being displayed or all logs (the intended meaning). Let's rephrase this as "Journal begins ..." to make this clearer.
* systemd-run: add --slice-inheritMarc-André Lureau2020-04-091-0/+14
| | | | Add a new option to easily place a slice within the systemd-run slice.
* man: correct the default slice for systemd-run unitsLennart Poettering2020-04-091-2/+4
| | | | As suggested in #15362
* run: propagate return code/status from the childZbigniew Jędrzejewski-Szmek2019-11-051-2/+17
| | | | | | | | | | | | | | | Fixes #13756. We were returning things that didn't make much sense: we would always use the exit_code value as the exit code. But it sometimes contains a exit code from the process, and sometimes the number of a signal that was used to kill the process. We would also ignore SuccessExitStatus= and in general whether systemd thinks the service exited successfully (hence the issue in #13756, where systemd would return success/SIGTERM, but we'd just look at the SIGTERM part.) If we are doing --wait, let's always propagate the exit code/status from the child. While at it, make the documentation useful.
* run: add -u as a synonym for --unitDavid Tardon2019-10-231-0/+1
| | | | | Other tools that do have --unit= option (journalctl and systemd-cgls) already do this, so let's be consistent.
* man: document the two new .timer settingsLennart Poettering2019-04-021-0/+12
|
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-2/+2
| | | | | | | The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
* man: standarize on one-line license headerZbigniew Jędrzejewski-Szmek2019-03-141-4/+1
| | | | | | No need to waste space, and uniformity is good. $ perl -i -0pe 's|\n+<!--\s*SPDX-License-Identifier: LGPL-2.1..\s*-->|\n<!-- SPDX-License-Identifier: LGPL-2.1+ -->|gms' man/*.xml
* run: add new --shell switch for spawning a shell as serviceLennart Poettering2018-11-231-0/+9
| | | | | | | | | I keep running "systemd-run -t /bin/bash" to quickly get a shell running in service context. I suspect I am not the only one, hence let's add a shortcut for it. While we are at it, let's make it smarter, and automatically inherit the $SHELL of the invoking user as well as the working directory, and let's imply --pty. --shell (or -S) is hence equivalent to "-t -d $SHELL".
* run: add a switch for specifiying the working directory of a serviceLennart Poettering2018-11-231-0/+17
| | | | | | | | | | | | I find myself testing service management quite often with "systemd-run -t /bin/bash". For that it is handy if the invoked shell would use the working directory I am currently in. Hence introduce a shorthand for that: $ systemd-run -dt /bin/bash This will automatically insert a WorkingDirectory= property into the transient service, pointing to the working directory of the caller.
* man: document the new Type=exec typeLennart Poettering2018-07-251-0/+10
| | | | | | And while we are at it, let's rearrange and extend the Type= documentation a bit. Let's make it an itemized list, and let's add a paragraph explaining which type best to use.
* man: drop mode line in file headersZbigniew Jędrzejewski-Szmek2018-07-031-1/+1
| | | | | This is already included in .dir-locals, so we don't need it in the files themselves.
* Merge pull request #9301 from keszybz/man-drop-authorgroupLennart Poettering2018-06-141-9/+0
|\ | | | | man: drop unused <authorgroup> tags from man sources
| * man: drop unused <authorgroup> tags from man sourcesZbigniew Jędrzejewski-Szmek2018-06-141-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
* | Drop my copyright headersZbigniew Jędrzejewski-Szmek2018-06-141-2/+0
|/ | | | | | | perl -i -0pe 's/\s*Copyright © .... Zbigniew Jędrzejewski.*?\n/\n/gms' man/*xml git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/(#\n)?# +Copyright © [0-9, -]+ Zbigniew Jędrzejewski.*?\n//gms' git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/\s*\/\*\*\*\s+Copyright © [0-9, -]+ Zbigniew Jędrzejewski[^\n]*?\s*\*\*\*\/\s*/\n\n/gms' git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/\s+Copyright © [0-9, -]+ Zbigniew Jędrzejewski[^\n]*//gms'
* tree-wide: beautify remaining copyright statementsLennart Poettering2018-06-141-1/+1
| | | | | | Let's unify an beautify our remaining copyright statements, with a unicode ©. This means our copyright statements are now always formatted the same way. Yay.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* man: run: add missing optionYu Watanabe2018-01-101-0/+1
|
* man: add explanation about transient path or socket units in systemd-runYu Watanabe2017-12-231-21/+40
|
* man: generalize "binary" to "program" (#7668)Alan Jenkins2017-12-161-2/+2
| | | | | | | | | | | Systemd services are permitted to be scripts, as well as binary executables. The same also applies to the underlying /sbin/mount and /sbin/swapon. It is not necessary for the user to consider what type of program file these are. Nor is it necessary with systemd-nspawn, to distinguish between init as a "binary" v.s. a user-specified "program". Also fix a couple of grammar nits in the modified sentences.
* Add SPDX license identifiers to man pagesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* run: add "-G" as shortcut for "--property=CollectMode=inactive-or-failed"Lennart Poettering2017-11-161-0/+15
| | | | | | | | | This option is likely to be very useful for systemd-run invocations, hence let's add a shortcut for it. With this new concepts it's now very easy to put together systemd-run invocations that leave zero artifacts in the system, including when they fail.
* man: document > /dev/stderr pitfalls (#7317)Lennart Poettering2017-11-141-1/+9
| | | | Fixes: #7254 See: #2473
* man: minor correction for systemd-runLennart Poettering2017-09-141-1/+1
| | | | | The meaning was acidentally inverted in 156d6036be8c4d64747b5919adf372c289d3423a, let's correct this.
* man: fix repeated use of "use" in a sentenceZbigniew Jędrzejewski-Szmek2017-09-131-4/+5
|
* run: add new --pipe option for including "systemd-run" commands in shell ↵Lennart Poettering2017-09-121-4/+21
| | | | | | | | | | | | | | pipelines In this mode, we'll directly connect stdin/stdout/stderr of the invoked service with whatever systemd-run itself is invoked on. This allows inclusion of "systemd-run" commands in shell pipelines, as unlike "--pty" this means EOF of stdin/stdout/stderr are propagated independently. If --pty and --pipe are combined systemd-run will automatically pick the right choice for the context it is invoked in, i.e. --pty when invoked on a TTY, and --pipe otherwise.
* man: document that systemd-run --on-* cannot be used with --ptyLucas Werkmeister2017-02-071-2/+2
|
* man: fix flag in systemd-run (#5107)Rike-Benjamin Schuppner2017-01-201-1/+1
|
* man: document that "systemd-run -M" propagates exit codes, and "machinectl ↵Lennart Poettering2016-12-271-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* man: typo fixesThomas Hindoe Paaboel Andersen2016-10-121-1/+1
| | | | A mix of fixes for typos and UK english
* man: document the new --wait switch of systemd-runLennart Poettering2016-08-221-94/+71
| | | | Also, make major improvements to the an page in general.
* add a new tool for creating transient mount and automount unitsLennart Poettering2016-08-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | This adds "systemd-mount" which is for transient mount and automount units what "systemd-run" is for transient service, scope and timer units. The tool allows establishing mounts and automounts during runtime. It is very similar to the usual /bin/mount commands, but can pull in additional dependenices on access (for example, it pulls in fsck automatically), an take benefit of the automount logic. This tool is particularly useful for mount removable file systems (such as USB sticks), as the automount logic (together with automatic unmount-on-idle), as well as automatic fsck on first access ensure that the removable file system has a high chance to remain in a fully clean state even when it is unplugged abruptly, and returns to a clean state on the next re-plug. This is a follow-up for #2471, as it adds a simple client-side for the transient automount logic added in that PR. In later work it might make sense to invoke this tool automatically from udev rules in order to implement a simpler and safer version of removable media management á la udisks.
* run: various minor improvementsLennart Poettering2016-08-181-1/+1
| | | | Let's improve the --help text a bit, and other changes.
* Merge pull request #3005 from keszybz/kill-user-procesesLennart Poettering2016-04-211-19/+74
|\ | | | | Kill user session scope by default
| * man: expand description of lingering and KillUserProcesses settingZbigniew Jędrzejewski-Szmek2016-04-211-0/+44
| | | | | | | | | | | | | | | | | | | | The description in the man page was wrong, KillUserProcesses does not kill all processes of the user. Describe what the setting does, and also add links between the relavant sections of the manual. Also, add an extensive example which shows how to launch screen in the background.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-11 15:43:04 +0100