summaryrefslogtreecommitdiffstats
path: root/shell-completion (follow)
Commit message (Collapse)AuthorAgeFilesLines
* bash-completion: add --list-devices to systemd-cryptenrollAntonio Alvarez Feijoo7 days1-9/+2
| | | | And also use it to list suitable block devices.
* busctl: various bugfixes + tweaks (#34928)Luca Boccassi2024-10-292-2/+2
|\ | | | | | | | | Fixes: #34048 Replaces: #34796 Follow-up for: #33961
| * busctl: rename --num-matches= → --limit-messages=Lennart Poettering2024-10-292-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We should avoid unnecessary abbreviations for such messages, and this puts a maximum limit on things, hence it should indicate this in the name. Moreover, matches is a bit confusing, since most people will probably call "busctl monitor" without any match specification, i.e. zero matches, but that's not what was meant here at all. Also, add a brief switch for this (-N) since I figure in particular "-N1" might be a frequent operation people might want to use. Follow-up for: 989e843e7543b21b91de4368da44692d674722a5 See: #34048
* | Merge pull request #34245 from bluca/logind_drop_weak_delay_inhibitorZbigniew Jędrzejewski-Szmek2024-10-291-1/+1
|\ \ | |/ |/| logind: drop new delay-weak inhibitor
| * logind: drop new delay-weak inhibitorLuca Boccassi2024-09-131-1/+1
| | | | | | | | | | | | | | | | It wasn't actually requested, just a misunderstanding, so drop it. Fixes https://github.com/systemd/systemd/issues/34091 Follow-up for 804874d26ac73e0af07c4c5d7165c95372f03f6d
* | bash-completion/busctl: support wait commandYu Watanabe2024-10-141-0/+13
| | | | | | | | Follow-up for 30465af656a10c124e7fa9fb33f7ad8454e9af2e.
* | busctl: add wait verb to wait for signalsRonan Pigott2024-10-131-0/+26
| | | | | | | | | | It's like busctl call, but it waits for a signal rather than a reply to a method call.
* | shell-completion/analyze: add has-tpm2Yu Watanabe2024-09-192-1/+2
|/
* Revert "nspawn: Allow specifying custom init program"Daan De Meyer2024-08-222-2/+1
| | | | | | | | | | I don't actually need this anymore since we're going with a unit based approach for the containers stuff internally so let's just revert it. Fixes #34085 This reverts commit ce2291730d5f91190e97e7c515ac772ae4970062.
* resolvectl: introduce --no-ask-password optionYu Watanabe2024-08-192-1/+3
|
* networkctl: introduce --no-ask-password optionYu Watanabe2024-08-192-2/+3
|
* shell-completion: zsh: fix incorrect unescapingbryango2024-08-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Previously the `_filter_units_by_property` completion function outputs with a [zsh parameter expansion flag] `g:o:`. This means that the returned result is unescaped as the zsh builtin `echo`, except that octal escapes don’t take a leading zero. This seemed to have worked back in the days when it was first introduced: 6c9414a700a040be1d3160bd2336baac58a1da3e But it now leads to incorrect over-unescaping; for example, system-systemd\\x2djournald.slice (correct) is incorrectly completed by zsh in commands such as `systemctl kill`: system-systemd-journald.slice (incorrect) This commit fixes such problems by removing the `g:o:` flag. See: [zsh parameter expansion flag]: https://zsh.sourceforge.io/Doc/Release/Expansion.html#Parameter-Expansion-Flags
* systemd-run: add unit and invocation_id JSON outputLukas Nykryn2024-08-122-1/+7
|
* busctl: add --num-matches= for monitor verbLuca Boccassi2024-08-092-1/+2
| | | | | Useful in scripts when one wants to wait for a specific signal before continuing
* busctl: add support for --timeout to monitor verbLuca Boccassi2024-08-081-1/+1
| | | | Useful in scripts when you want to exit successfully after a certain time
* nspawn: Allow specifying custom init programDaan De Meyer2024-08-062-1/+2
| | | | | | This allows for example forcing to use /sbin/init instead of always using /usr/lib/systemd/systemd if it exists. Or it allows using a different path altogether.
* systemd-analyze: Add svg scaling optionsrajmohan r2024-08-051-1/+1
| | | | | | | + Scale the x-axis of the resulting plot by a factor (default 1.0) + Add activation timestamps to each bar Signed-off-by: rajmohan r <rajmohan.r@kpit.com>
* localectl: introduce -l/--full optionYu Watanabe2024-08-022-1/+2
| | | | Closes #33906.
* journalctl: add --list-invocations command and -I/--invocation optionsYu Watanabe2024-08-011-2/+2
| | | | | | | | | The --list-invocations command is similar to --list-boots, but shows invocation IDs of specified unit. This should be useful when showing a specific invocation of a unit. The --invocation option is similar to --boot, but takes a invocation ID or an offset. The -I option is equivalent to --invocation=0.
* Merge pull request #30307 from bluca/enforce_inhibitorsZbigniew Jędrzejewski-Szmek2024-07-261-1/+1
|\ | | | | logind: always check for inhibitor locks
| * logind: always check for inhibitor locksLuca Boccassi2024-07-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently inhibitors are bypassed unless an explicit request is made to check for them, or even in that case when the requestor is root or the same uid as the holder of the lock. But in many cases this makes it impractical to rely on inhibitor locks. For example, in Debian there are several convoluted and archaic workarounds that divert systemctl/reboot to some hacky custom scripts to try and enforce blocking accidental reboots, when it's not expected that the requestor will remember to specify the command line option to enable checking for active inhibitor locks. Also in many cases one wants to ensure that locks taken by a user are respected by actions initiated by that same user. Change logind so that inhibitors checks are not skipped in these cases, and systemctl so that locks are checked in order to show a friendly error message rather than "permission denied". Add new block-weak and delay-weak modes that keep the previous behaviour unchanged.
* | shell completion: add support for sd-analyze capability --maskLuca Boccassi2024-07-251-1/+7
|/ | | | Follow-up for 3e7a029c2856e7814b930443cc2d4fb089377592
* zsh/_networkctl: remove duplicated argument for completion (#31926)Collin L2024-07-221-1/+1
| | | It is unnecessary, which will mess the completion.
* zsh: update varlinkctl completionsRonan Pigott2024-07-191-8/+26
| | | | | | | | | | | | | | | correct redundant or mismatched tags and fill the argument field of curcontext because _regex_words does not do that for us. The _complete_help text now looks much more reasonable most of the time: $ varlinkctl call /run/systemd/resolve/io.systemd.Resolve ^Xh tags in context :completion::complete:varlinkctl:: argument-rest (_arguments _varlinkctl) tags in context :completion::complete:varlinkctl-call:method: varlink-methods (_varlinkctl_cmd _varlinkctl_command _arguments _varlinkctl) Fixes: af63b4b769bf ("zsh: add varlinkctl completions")
* zsh: add varlinkctl completionsRonan Pigott2024-07-192-0/+53
|
* id128: add 'var-partition-uuid' verbLuca Boccassi2024-07-171-1/+1
| | | | | | | As per DPS the UUID for /var/ should be keyed by the local machine-id, which is non-trivial to do in a script. Enhance 'systemd-id128' to take 'var-partition-uuid' as a verb, and if so perform the calculation.
* zsh: add run0 completionsRonan Pigott2024-07-042-0/+58
|
* cryptenroll: support for enrolling FIDO2 tokens in manual modeKamil Szczęk2024-06-201-2/+4
| | | | | | | | | | | | | | systemd-cryptsetup supports a FIDO2 mode with manual parameters, where the user provides all the information necessary for recreating the secret, such as: credential ID, relaying party ID and the salt. This feature works great for implementing 2FA schemes, where the salt file is for example a secret unsealed from the TPM or some other source. While the unlocking part is quite straightforward to set up, enrolling such a keyslot - not so easy. There is no clearly documented way on how to set this up and online resources are scarce on this topic too. By implementing a straightforward way to enroll such a keyslot directly from systemd-cryptenroll we streamline the enrollment process and reduce chances for user error when doing such things manually.
* bootctl: add --random-seed=yes/noLudwig Nussel2024-06-202-1/+5
|
* shell-completion: only offer devices for completionDavid Tardon2024-06-121-4/+1
| | | | | This skips directories and other stuff like /dev/core, /dev/initctl or /dev/log.
* shell-completion: update bash completion for networkctlYu Watanabe2024-06-111-3/+24
|
* shell-completion: update bash-completion for udevadmYu Watanabe2024-06-111-12/+31
| | | | | | | - Add missing options. - Show device nodes when supported. Closes #33265.
* shell-completion: add systemd-vmspawn to meson.buildArthur Zamarin2024-05-181-0/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add missing args to bash systemd-nspawnArthur Zamarin2024-05-181-3/+3
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add missing args to bash systemd-runArthur Zamarin2024-05-181-13/+15
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: on zsh, systemd-cat is a precommandhydrargyrum2024-05-091-2/+2
| | | | | _precommand lets zsh complete other commands and their arguments e.g. it can complete grep with "systemd-cat gr" and complete grep options with "systemd-cat grep -"
* shell-completion: add bash completion for systemd-vmspawnArthur Zamarin2024-05-011-0/+70
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add missing args to zsh resolvectlArthur Zamarin2024-05-011-0/+12
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add missing args to bash resolvectlArthur Zamarin2024-05-011-8/+8
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add missing args to bash systemd-analyzeArthur Zamarin2024-05-011-3/+11
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add bash-completion for systemd-vpick commandArthur Zamarin2024-04-262-0/+61
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completion: add bash-completion for run0 commandArthur Zamarin2024-04-262-0/+114
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell-completions: install new completions which were forgottenArthur Zamarin2024-04-261-0/+2
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell completion: fix machinectl import-{tar,raw}Arthur Zamarin2024-04-261-2/+6
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* shell completion: add bash completion for importctlArthur Zamarin2024-04-261-0/+125
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* Merge pull request #32144 from bluca/portable_cleanLuca Boccassi2024-04-181-1/+2
|\ | | | | portablectl: add --clean parameter for detaching
| * bash completion: add missing parameters for portablectlLuca Boccassi2024-04-181-1/+1
| |
| * portablectl: add --clean parameter for detachingLuca Boccassi2024-04-181-1/+2
| | | | | | | | | | Calls CleanUnit on each portable service being removed, after it has stopped
* | systemctl: add --clean= values to documentation and shell completionLuca Boccassi2024-04-181-1/+1
|/
* improve zsh completion (#32098)Eisuke Kawashima2024-04-1523-217/+239
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fix error * remove options that are no longer supported * add missing options * stop completion if an option `--help` or `--version` is supplied [[[ zjs: a note for the reader: zshcompsys(1) in the section about optspecs in _arguments says: > Each of the forms above may be preceded by a list in parentheses of option names and argument num‐ > bers. If the given option is on the command line, the options and arguments indicated in parentheses > will not be offered. For example, ‘(-two -three 1)-one:...' completes the option ‘-one'; if this ap‐ > pears on the command line, the options -two and -three and the first ordinary argument will not be > completed after it. ‘(-foo):...' specifies an ordinary argument completion; -foo will not be com‐ > pleted if that argument is already present. > > Other items may appear in the list of excluded options to indicate various other items that should > not be applied when the current specification is matched: a single star (\*) for the rest arguments > (i.e. a specification of the form ‘\*:...'); a colon (:) for all normal (non-option-) arguments; and a > hyphen (-) for all options. For example, if ‘(\*)' appears before an option and the option appears on > the command line, the list of remaining arguments (those shown in the above table beginning with > ‘\*:') will not be completed. The intended effect of the change is to remove irrelevant completion matches from the completion. tl;dr: (- : ) prevents further completion ]]]