summaryrefslogtreecommitdiffstats
path: root/man/systemctl.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* systemctl,pid1: do not warn about missing install info with "preset"Zbigniew Jędrzejewski-Szmek2016-04-221-13/+13
| | | | | | | | | | | | | | When "preset" was executed for a unit without install info, we'd warn similarly as for "enable" and "disable". But "preset" is usually called for all units, because the preset files are provided by the distribution, and the units are under control of individual programs, and it's reasonable to call "preset" for all units rather then try to do it only for the ones that can be installed. We also don't warn about missing info for "preset-all". Thus it seems reasonable to silently ignore units w/o install info when presetting. (In addition, when more than one unit was specified, we'd issue the warning only if none of them had install info. But this is probably something to fix for enable/disable too.)
* core,systemctl: add new "systemctl revert" commandLennart Poettering2016-04-121-0/+22
| | | | | | This allows dropping all user configuration and reverting back to the vendor default of a unit file. It basically undoes what "systemctl edit", "systemctl set-property" and "systemctl mask" do.
* install: introduce a new unit file state "transient"Lennart Poettering2016-04-121-0/+5
| | | | | | Now, that the search path logic knows the unit path for transient units we also can introduce an explicit unit file state "transient" that clarifies to the user what kind of unit file he is encountering.
* core: add a new unit file state "generated"Lennart Poettering2016-04-121-4/+9
| | | | | | | | Now that we store the generator directories in LookupPaths we can use this to intrdouce a new unit file state called "generated", for units in these directories. Fixes: #2348
* systemctl: add --value optionZbigniew Jędrzejewski-Szmek2016-04-051-0/+10
| | | | | | | | | | With this option, systemctl will only print the rhs in show: $ systemctl show -p Wants,After systemd-journald --value systemd-journald.socket ... systemd-journald-dev-log.socket ... This is useful in scripts, because the need to call awk or similar is removed.
* man: follow up fixes for #2575Zbigniew Jędrzejewski-Szmek2016-02-111-12/+7
|
* man: correct explanation of "systemctl is-enabled" outputLennart Poettering2016-02-101-1/+1
| | | | | | | | The "is-enabled" command doesn't care whether the symlinks are declared in the [Install] section of a unit file or not, when returning "enabled". Any alias, .wants/ or .requires/ symlinks suffice. Fixes: #975
* man: document that "systemctl enable" supports abbreviated unit file namesLennart Poettering2016-02-101-4/+3
| | | | Fixes: #1502
* systemctl: rename "reload-or-try-restart" verb to "try-reload-or-restart"Lennart Poettering2016-01-281-1/+1
| | | | | | | | But also keep the old name as (undocumented) compatibility around. The reload-or-try-restart was documented to be a NOP if the unit is not running, since the previous commits this is also implemented. The old name suggests that the "try" logic only applies to restarting. Fix this, by moving the "try-" to the front, to indicate that the whole option is a NOP if the service isn't running.
* man: stop documenting legacy RedHatismsLennart Poettering2016-01-281-6/+6
| | | | | We generally document only the supported verbs, but not the compatibility verbs we also support, in order to keep the documentation minimal.
* Merge branch 'pr/980'Daniel Mack2016-01-271-1/+1
|\
| * man: make systemctl is-enabled description match enable.Andrei Borzenkov2016-01-271-1/+1
| | | | | | | | | | systemctl is-enabled is not limited to wants.d - it also checks for requires.d and alias links.
* | man: document that unit file globbing only operates on primary unit namesLennart Poettering2016-01-271-15/+12
|/ | | | See: #2397
* man: fix typosJakub Wilk2015-12-261-1/+1
|
* man: fix typo in systemctl(1)Michael Biebl2015-12-211-1/+1
|
* core: allow 'SetUnitProperties()' to run on inactive units tooFranck Bui2015-11-221-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 'set-property' has been primarly designed to change some properties of *active* units. However it can easily work on inactive units as well. In that case changes are only saved in a drop-in for futur uses and changes will be effective when unit will be started. Actually it already works on inactive units but that was not documented and not fully supported. Indeed the inactive units had to be known by the manager otherwise it was reported as not loaded: $ systemctl status my-test.service * my-test.service - My Testing Unit Loaded: loaded (/etc/systemd/system/my-test.service; static; vendor preset: disabled) Drop-In: /etc/systemd/system/my-test.service.d Active: inactive (dead) $ systemctl set-property my-test.service MemoryLimit=1000000 Failed to set unit properties on my-test.service: Unit my-test.service is not loaded. [ Note: that the unit load state reported by the 'status' command might be confusing since it claimed the unit as loaded but 'set-property' reported the contrary. ] One can possibily workaround this by making the unit a dependency of another active unit so the manager will keep it around: $ systemctl add-wants multi-user.target my-test.service Created symlink from /etc/systemd/system/multi-user.target.wants/my-test.service to /etc/systemd/system/my-test.service. $ systemctl set-property my-test.service MemoryLimit=1000000 $ systemctl status my-test.service * my-test.service - My Testing Unit Loaded: loaded (/etc/systemd/system/my-test.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/my-test.service.d `-50-MemoryLimit.conf Active: inactive (dead) This patch simply forces 'SetUnitProperties()' to load the unit if it's not already the case. It also documents the fact that 'set-property' can be used on inactive units.
* Merge pull request #1869 from poettering/kill-overridableMichal Schmidt2015-11-131-3/+0
|\ | | | | Remove support for RequiresOverridable= and RequisiteOverridable=
| * core: remove support for RequiresOverridable= and RequisiteOverridable=Lennart Poettering2015-11-121-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As discussed at systemd.conf 2015 and on also raised on the ML: http://lists.freedesktop.org/archives/systemd-devel/2015-November/034880.html This removes the two XyzOverridable= unit dependencies, that were basically never used, and do not enhance user experience in any way. Most folks looking for the functionality this provides probably opt for the "ignore-dependencies" job mode, and that's probably a good idea. Hence, let's simplify systemd's dependency engine and remove these two dependency types (and their inverses). The unit file parser and the dbus property parser will now redirect the settings/properties to result in an equivalent non-overridable dependency. In the case of the unit file parser we generate a warning, to inform the user. The dbus properties for this unit type stay available on the unit objects, but they are now hidden from usual introspection and will always return the empty list when queried. This should provide enough compatibility for the few unit files that actually ever made use of this.
* | man: improve the unit file enable state table a bitLennart Poettering2015-11-121-4/+4
| |
* | install: follow unit file symlinks in /usr, but not /etc when looking for ↵Lennart Poettering2015-11-121-4/+10
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [Install] data Some distributions use alias unit files via symlinks in /usr to cover for legacy service names. With this change we'll allow "systemctl enable" on such aliases. Previously, our rule was that symlinks are user configuration that "systemctl enable" + "systemctl disable" creates and removes, while unit files is where the instructions to do so are store. As a result of the rule we'd never read install information through symlinks, since that would mix enablement state with installation instructions. Now, the new rule is that only symlinks inside of /etc are configuration. Unit files, and symlinks in /usr are now valid for installation instructions. This patch is quite a rework of the whole install logic, and makes the following addional changes: - Adds a complete test "test-instal-root" that tests the install logic pretty comprehensively. - Never uses canonicalize_file_name(), because that's incompatible with operation relative to a specific root directory. - unit_file_get_state() is reworked to return a proper error, and returns the state in a call-by-ref parameter. This cleans up confusion between the enum type and errno-like errors. - The new logic puts a limit on how long to follow unit file symlinks: it will do so only for 64 steps at max. - The InstallContext object's fields are renamed to will_process and has_processed (will_install and has_installed) since they are also used for deinstallation and all kinds of other operations. - The root directory is always verified before use. - install.c is reordered to place the exported functions together. - Stricter rules are followed when traversing symlinks: the unit suffix must say identical, and it's not allowed to link between regular units and templated units. - Various modernizations - The "invalid" unit file state has been renamed to "bad", in order to avoid confusion between UNIT_FILE_INVALID and _UNIT_FILE_STATE_INVALID. Given that the state should normally not be seen and is not documented this should not be a problematic change. The new name is now documented however. Fixes #1375, #1718, #1706
* Remove snapshot unit typeZbigniew Jędrzejewski-Szmek2015-11-111-40/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Snapshots were never useful or used for anything. Many systemd developers that I spoke to at systemd.conf2015, didn't even know they existed, so it is fairly safe to assume that this type can be deleted without harm. The fundamental problem with snapshots is that the state of the system is dynamic, devices come and go, users log in and out, timers fire... and restoring all units to some state from the past would "undo" those changes, which isn't really possible. Tested by creating a snapshot, running the new binary, and checking that the transition did not cause errors, and the snapshot is gone, and snapshots cannot be created anymore. New systemctl says: Unknown operation snapshot. Old systemctl says: Failed to create snapshot: Support for snapshots has been removed. IgnoreOnSnaphost settings are warned about and ignored: Support for option IgnoreOnSnapshot= has been removed and it is ignored http://lists.freedesktop.org/archives/systemd-devel/2015-November/034872.html
* doc: correct orthography, word forms and missing/extraneous wordsJan Engelhardt2015-11-061-11/+11
|
* doc: correct punctuation and improve typography in documentationJan Engelhardt2015-11-061-10/+10
|
* systemctl: update documentation for --plain optionMark Theunissen2015-11-041-1/+3
| | | | - Existing documentation did not mention that --plain omits the bullets and works on list-units and list-machines.
* Merge pull request #1419 from keszybz/shell-completionLennart Poettering2015-09-301-4/+8
|\ | | | | Shell completion tweaks
| * systemctl: add --state=helpZbigniew Jędrzejewski-Szmek2015-09-281-4/+8
| | | | | | | | | | | | This mirrors --type=help and simplifies completion scripts. The array of states is dense, so the is no need to check if the string is null.
* | systemctl: make "systemctl is-system-running" return "offline" if we are not ↵Lennart Poettering2015-09-291-13/+37
|/ | | | | | | | | | | | | | booted with systemd This sounds like the better place to expose this than in "systemd-notify --booted". Also document the so far undocumented "unknown" state the command might return. And rearrange the table of states documented to be more like the one for "is-running". Also, don't document the precise exit code of this function, just say errors are reported != 0 or > 0...
* containers: systemd exits with non-zero codeAlban Crequy2015-09-211-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a systemd service running in a container exits with a non-zero code, it can be useful to terminate the container immediately and get the exit code back to the host, when systemd-nspawn returns. This was not possible to do. This patch adds the following to make it possible: - Add a read-only "ExitCode" property on PID 1's "Manager" bus object. By default, it is 0 so the behaviour stays the same as previously. - Add a method "SetExitCode" on the same object. The method fails when called on baremetal: it is only allowed in containers or in user session. - Add support in systemctl to call "systemctl exit 42". It reuses the existing code for user session. - Add exit.target and systemd-exit.service to the system instance. - Change main() to actually call systemd-shutdown to exit() with the correct value. - Add verb 'exit' in systemd-shutdown with parameter --exit-code - Update systemctl manpage. I used the following to test it: | $ sudo rkt --debug --insecure-skip-verify run \ | --mds-register=false --local docker://busybox \ | --exec=/bin/chroot -- /proc/1/root \ | systemctl --force exit 42 | ... | Container rkt-895a0cba-5c66-4fa5-831c-e3f8ddc5810d failed with error code 42. | $ echo $? | 42 Fixes https://github.com/systemd/systemd/issues/1290
* core: extend KillUnit() to return error when no unit was killedJan Synacek2015-09-211-0/+11
|
* systemctl: add ConsistsOf as the inverse of PartOfEvgeny Vereshchagin2015-09-081-0/+1
|
* logind/systemctl: introduce SetWallMessage and --messageJan Synacek2015-08-251-0/+12
| | | | | | | | | | | | | Enable unprivileged users to set wall message on a shutdown operation. When the message is set via the --message option, it is logged together with the default shutdown message. $ systemctl reboot --message "Applied kernel updates." $ journalctl -b -1 ... systemd-logind[27]: System is rebooting. (Applied kernel updates.) ...
* man: update description of --quietZbigniew Jędrzejewski-Szmek2015-08-061-8/+5
| | | | | | | | This description should provide the general rule, without listing all the subcommands, which is bound to get out of date too often. https://github.com/systemd/systemd/issues/216
* man: information about available propertiesZbigniew Jędrzejewski-Szmek2015-07-021-5/+23
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=1144496
* man: Remove instances of pseudo-English "resp."Andrew Eikum2015-06-291-3/+3
| | | | | | | Me again :) Just noticed one of these in a manpage and did another pass to clean them up. See 16dad32e437fdf2ffca03cc60a083d84bd31886f for explanation, though the link needs updating: <http://transblawg.eu/2004/02/26/resp-and-other-non-existent-english-wordsnicht-existente-englische-worter/>
* systemctl: Use /usr/bin/editor if availableMichael Biebl2015-06-031-0/+1
| | | | | | | | | | | | | If the EDITOR environment variable is not set, the Debian policy recommends to use the /usr/bin/editor program as default editor. This file is managed via the dpkg alternatives mechanism and typically used in Debian/Ubuntu and derivatives to configure the default editor. See section 11.4 of the Debian policy [1]. Therefor prefer /usr/bin/editor over specific editors if available. [1] https://www.debian.org/doc/debian-policy/ch-customized-programs.html
* man: use configured path for mount and umount binaries in manpagesFilipe Brandenburger2015-05-281-2/+2
| | | | | | | | | | | Export the MOUNT_PATH and UMOUNT_PATH variables as XML entities and use them in the systemctl.1 manpage instead of hardcoding the path in /usr/bin. Tested: - Ran ./configure ac_cv_path_MOUNT_PATH=/bin/mount (same for umount) and rebuilt the manpages, confirmed that the correct path was in man/systemctl.1 - Rebuilt man/systemd.directives.xml and the man pages derived from it, confirmed that the correct paths were there as well.
* man: generate configured paths in manpagesFilipe Brandenburger2015-05-281-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In particular, use /lib/systemd instead of /usr/lib/systemd in distributions like Debian which still have not adopted a /usr merge setup. Use XML entities from man/custom-entities.ent to replace configured paths while doing XSLT processing of the original XML files. There was precedent of some files (such as systemd.generator.xml) which were already using this approach. This addresses most of the (manual) fixes from this patch: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/Fix-paths-in-man-pages.patch?h=experimental-220 The idea of using generic XML entities was presented here: http://lists.freedesktop.org/archives/systemd-devel/2015-May/032240.html This patch solves almost all the issues, with the exception of: - Path to /bin/mount and /bin/umount. - Generic statements about preference of /lib over /etc. These will be handled separately by follow up patches. Tested: - With default configure settings, ran "make install" to two separate directories and compared the output to confirm they matched exactly. - Used a set of configure flags including $CONFFLAGS from Debian: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules Installed the tree and confirmed the paths use /lib/systemd instead of /usr/lib/systemd and that no other unexpected differences exist. - Confirmed that `make distcheck` still passes.
* Use "new" --job-mode= option in more placesZbigniew Jędrzejewski-Szmek2015-05-181-4/+4
| | | | | | --irreversible/--ignore-dependencies/--fail are deprececated since 4dc5b821ae737914499119e29811fc3346e3d97c. Also add shell completions for --jobs-mode.
* systemctl: introduce --now for enable, disable and maskJan Synacek2015-05-151-9/+24
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=42940
* treewide: Correct typos and spell plural of bus consistentTorstein Husebø2015-05-111-1/+1
|
* run: by default, wait until the transient unit finished start-upLennart Poettering2015-04-281-2/+2
| | | | | Make this blocking behaviour optional with --no-block, similar to systemctl's switch of this name.
* logind,systemctl: add reboot to EFI firmware supportJan Janssen2015-04-071-0/+12
|
* man: fix name of systemd.resource-control(5)Zbigniew Jędrzejewski-Szmek2015-03-141-1/+1
|
* man: fix a bunch of linksZbigniew Jędrzejewski-Szmek2015-03-141-3/+3
| | | | All hail linkchecker!
* man: boilerplate unificationZbigniew Jędrzejewski-Szmek2015-02-111-15/+15
|
* man: fix reference to glob manpageZbigniew Jędrzejewski-Szmek2015-02-111-3/+3
|
* man: add systemd.generator(7)Zbigniew Jędrzejewski-Szmek2015-02-111-6/+11
| | | | | | | | | This is largely based on http://www.freedesktop.org/wiki/Software/systemd/Generators/, and obsoletes that page. It seems that we do a much better job of keeping man pages up-to-date compared to wiki pages. Man pages are also easier to find for users. https://bugs.freedesktop.org/show_bug.cgi?id=89048
* man: use one description of --no-legendZbigniew Jędrzejewski-Szmek2015-01-201-10/+2
|
* systemctl: fix import-environment description, trim help to 80 colsZbigniew Jędrzejewski-Szmek2015-01-191-1/+4
|
* man: remove references to systemadm from systemctl man pageLennart Poettering2015-01-081-1/+1
| | | | The tool is badly maintained and we shouldn't refence such old cruft.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-13 00:20:48 +0100