summaryrefslogtreecommitdiff
path: root/man
AgeCommit message (Collapse)AuthorFilesLines
2019-07-24man: highlight the different concepts behind h/H and t/TLennart Poettering1-33/+34
Fixes: #13151
2019-07-23core: rename ShutdownWatchdogSec to RebootWatchdogSecLuca Boccassi1-4/+4
This option is only used on reboot, not on other types of shutdown modes, so it is misleading. Keep the old name working for backward compatibility, but remove it from the documentation.
2019-07-23core: add KExecWatchdogSec optionLuca Boccassi1-1/+8
Rather than always enabling the shutdown WD on kexec, which might be dangerous in case the kernel driver and/or the hardware implementation does not reset the wd on kexec, add a new timer, disabled by default, to let users optionally enable the shutdown WD on kexec separately from the runtime and reboot ones. Advise in the documentation to also use the runtime WD in conjunction with it. Fixes: a637d0f9ecbe ("core: set shutdown watchdog on kexec too")
2019-07-22timedated: add back support for ntp-units.d/Zbigniew Jędrzejewski-Szmek2-35/+45
We removed support for foreign services (and ntp-units.d/) in b72ddf0f4. Support for foreign services was added back in 5d280742, but through an environment variable. The problem with the env var approach is that it only works as a mechanism to select one item, and doesn't work nicely as a mechinism to create a list of items through drop-ins (because the env var can be easily overridden, but not extended). Having a list of "ntp providers" is important to be able to reliably disable all of them when that is requested. Another problem is that nobody ever bothered to care about our new "standard". ntp-units.d/ is a nice simple format that works and is already supported by chrony and ntpd and timedatex. If we were to introduce and ask people to follow a new standard, there should be some good reason for this. The idea with env vars has lower functionality, requires systemd-specific syntax. We should just re-adopt the format that we originally introduced and that seems to work for everyone, and more on to more interesting problems.
2019-07-22man: describe $LESS options more fullyZbigniew Jędrzejewski-Szmek1-5/+30
https://bugzilla.redhat.com/show_bug.cgi?id=1655316
2019-07-19Merge pull request #13096 from keszybz/unit-loadingZbigniew Jędrzejewski-Szmek1-26/+32
Preparatory work for the unit loading rework
2019-07-19pstore: Tool to archive contents of pstoreEric DeVolder3-0/+190
This patch introduces the systemd pstore service which will archive the contents of the Linux persistent storage filesystem, pstore, to other storage, thus preserving the existing information contained in the pstore, and clearing pstore storage for future error events. Linux provides a persistent storage file system, pstore[1], that can store error records when the kernel dies (or reboots or powers-off). These records in turn can be referenced to debug kernel problems (currently the kernel stuffs the tail of the dmesg, which also contains a stack backtrace, into pstore). The pstore file system supports a variety of backends that map onto persistent storage, such as the ACPI ERST[2, Section 18.5 Error Serialization] and UEFI variables[3 Appendix N Common Platform Error Record]. The pstore backends typically offer a relatively small amount of persistent storage, e.g. 64KiB, which can quickly fill up and thus prevent subsequent kernel crashes from recording errors. Thus there is a need to monitor and extract the pstore contents so that future kernel problems can also record information in the pstore. The pstore service is independent of the kdump service. In cloud environments specifically, host and guest filesystems are on remote filesystems (eg. iSCSI or NFS), thus kdump relies [implicitly and/or explicitly] upon proper operation of networking software *and* hardware *and* infrastructure. Thus it may not be possible to capture a kernel coredump to a file since writes over the network may not be possible. The pstore backend, on the other hand, is completely local and provides a path to store error records which will survive a reboot and aid in post-mortem debugging. Usage Notes: This tool moves files from /sys/fs/pstore into /var/lib/systemd/pstore. To enable kernel recording of error records into pstore, one must either pass crash_kexec_post_notifiers[4] to the kernel command line or enable via 'echo Y > /sys/module/kernel/parameters/crash_kexec_post_notifiers'. This option invokes the recording of errors into pstore *before* an attempt to kexec/kdump on a kernel crash. Optionally, to record reboots and shutdowns in the pstore, one can either pass the printk.always_kmsg_dump[4] to the kernel command line or enable via 'echo Y > /sys/module/printk/parameters/always_kmsg_dump'. This option enables code on the shutdown path to record information via pstore. This pstore service is a oneshot service. When run, the service invokes systemd-pstore which is a tool that performs the following: - reads the pstore.conf configuration file - collects the lists of files in the pstore (eg. /sys/fs/pstore) - for certain file types (eg. dmesg) a handler is invoked - for all other files, the file is moved from pstore - In the case of dmesg handler, final processing occurs as such: - files processed in reverse lexigraphical order to faciliate reconstruction of original dmesg - the filename is examined to determine which dmesg it is a part - the file is appended to the reconstructed dmesg For example, the following pstore contents: root@vm356:~# ls -al /sys/fs/pstore total 0 drwxr-x--- 2 root root 0 May 9 09:50 . drwxr-xr-x 7 root root 0 May 9 09:50 .. -r--r--r-- 1 root root 1610 May 9 09:49 dmesg-efi-155741337601001 -r--r--r-- 1 root root 1778 May 9 09:49 dmesg-efi-155741337602001 -r--r--r-- 1 root root 1726 May 9 09:49 dmesg-efi-155741337603001 -r--r--r-- 1 root root 1746 May 9 09:49 dmesg-efi-155741337604001 -r--r--r-- 1 root root 1686 May 9 09:49 dmesg-efi-155741337605001 -r--r--r-- 1 root root 1690 May 9 09:49 dmesg-efi-155741337606001 -r--r--r-- 1 root root 1775 May 9 09:49 dmesg-efi-155741337607001 -r--r--r-- 1 root root 1811 May 9 09:49 dmesg-efi-155741337608001 -r--r--r-- 1 root root 1817 May 9 09:49 dmesg-efi-155741337609001 -r--r--r-- 1 root root 1795 May 9 09:49 dmesg-efi-155741337710001 -r--r--r-- 1 root root 1770 May 9 09:49 dmesg-efi-155741337711001 -r--r--r-- 1 root root 1796 May 9 09:49 dmesg-efi-155741337712001 -r--r--r-- 1 root root 1787 May 9 09:49 dmesg-efi-155741337713001 -r--r--r-- 1 root root 1808 May 9 09:49 dmesg-efi-155741337714001 -r--r--r-- 1 root root 1754 May 9 09:49 dmesg-efi-155741337715001 results in the following: root@vm356:~# ls -al /var/lib/systemd/pstore/155741337/ total 92 drwxr-xr-x 2 root root 4096 May 9 09:50 . drwxr-xr-x 4 root root 40 May 9 09:50 .. -rw-r--r-- 1 root root 1610 May 9 09:50 dmesg-efi-155741337601001 -rw-r--r-- 1 root root 1778 May 9 09:50 dmesg-efi-155741337602001 -rw-r--r-- 1 root root 1726 May 9 09:50 dmesg-efi-155741337603001 -rw-r--r-- 1 root root 1746 May 9 09:50 dmesg-efi-155741337604001 -rw-r--r-- 1 root root 1686 May 9 09:50 dmesg-efi-155741337605001 -rw-r--r-- 1 root root 1690 May 9 09:50 dmesg-efi-155741337606001 -rw-r--r-- 1 root root 1775 May 9 09:50 dmesg-efi-155741337607001 -rw-r--r-- 1 root root 1811 May 9 09:50 dmesg-efi-155741337608001 -rw-r--r-- 1 root root 1817 May 9 09:50 dmesg-efi-155741337609001 -rw-r--r-- 1 root root 1795 May 9 09:50 dmesg-efi-155741337710001 -rw-r--r-- 1 root root 1770 May 9 09:50 dmesg-efi-155741337711001 -rw-r--r-- 1 root root 1796 May 9 09:50 dmesg-efi-155741337712001 -rw-r--r-- 1 root root 1787 May 9 09:50 dmesg-efi-155741337713001 -rw-r--r-- 1 root root 1808 May 9 09:50 dmesg-efi-155741337714001 -rw-r--r-- 1 root root 1754 May 9 09:50 dmesg-efi-155741337715001 -rw-r--r-- 1 root root 26754 May 9 09:50 dmesg.txt where dmesg.txt is reconstructed from the group of related dmesg-efi-155741337* files. Configuration file: The pstore.conf configuration file has four settings, described below. - Storage : one of "none", "external", or "journal". With "none", this tool leaves the contents of pstore untouched. With "external", the contents of the pstore are moved into the /var/lib/systemd/pstore, as well as logged into the journal. With "journal", the contents of the pstore are recorded only in the systemd journal. The default is "external". - Unlink : is a boolean. When "true", the default, then files in the pstore are removed once processed. When "false", processing of the pstore occurs normally, but the pstore files remain. References: [1] "Persistent storage for a kernel's dying breath", March 23, 2011. https://lwn.net/Articles/434821/ [2] "Advanced Configuration and Power Interface Specification", version 6.2, May 2017. https://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf [3] "Unified Extensible Firmware Interface Specification", version 2.8, March 2019. https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf [4] "The kernel’s command-line parameters", https://static.lwn.net/kerneldoc/admin-guide/kernel-parameters.html
2019-07-19Merge pull request #13070 from yuwata/network-set-route-to-dhcp-dnsZbigniew Jędrzejewski-Szmek1-0/+8
2019-07-19docs: typo in arg name replace-irreversible -> replace-irreversiblyAnita Zhang1-6/+6
2019-07-19meson: update hint in man/rules/Zbigniew Jędrzejewski-Szmek1-0/+2
2019-07-19network: add DHCPv4.RoutesToDNS= settingYu Watanabe1-0/+8
2019-07-18Merge pull request #13102 from mbiebl/nologin-pathZbigniew Jędrzejewski-Szmek2-4/+4
meson: make nologin path build time configurable
2019-07-18man: add note about systemctl stop return valueZbigniew Jędrzejewski-Szmek1-2/+8
Fixes #13104. (I know a lot more could be added to that man page. This patch only addresses that once specific complaint.)
2019-07-18meson: make nologin path build time configurableMichael Biebl2-4/+4
Some distros install nologin as /usr/sbin/nologin, others as /sbin/nologin. Since we can't really on merged-usr everywhere (where the path wouldn't matter), make the path build time configurable via -Dnologin-path=. Closes #13028
2019-07-17Merge pull request #13047 from niedbalski/fix-5552-prLennart Poettering1-1/+2
resolved: add new option to only cache positive answers
2019-07-17resolved: switch cache option to a tri-state option (systemd#5552).Jorge Niedbalski1-1/+2
Change the resolved.conf Cache option to a tri-state "no, no-negative, yes" values. If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See systemd#5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. This change adds the 'no-negative' option when set it avoids putting in cache negative answers but still works the same heuristics for positive answers. Signed-off-by: Jorge Niedbalski <jnr@metaklass.org>
2019-07-17man: fix wrong section nameYu Watanabe1-1/+1
2019-07-17man: rework the description of Aliases and .wants/.requires directoriesZbigniew Jędrzejewski-Szmek1-26/+32
The description of Alias= wasn't incorrect, but it sounded like Alias= creates a different type of dependency, while it's just a glorified way to create symlinks. Also recommend 'preset' in addition to 'enable'. Describe .wants/.requires dirs as equals, without implying that the [Install] section can only be used for .wants. The text was partially out of date (systemd-networkd.service now creates as alias in /etc, not /usr/lib, let's just not say anything about the full path).
2019-07-17Merge pull request #12675 from yuwata/network-set-dnsLennart Poettering2-5/+16
resolvectl: support to modify interfaces managed by networkd
2019-07-17core: ExecCondition= for servicesAnita Zhang1-0/+20
Closes #10596
2019-07-17timedatectl: add 'ntp-servers' and 'revert' commands to modify link NTP serversYu Watanabe1-0/+14
2019-07-17resolvectl: support networkd managed interfacesYu Watanabe1-5/+2
Closes #9808.
2019-07-16doc: update explanation of IPv6AcceptRA=Yu Watanabe1-9/+9
2019-07-15network: show known route protocol name nicely in debugging logsYu Watanabe1-2/+2
2019-07-14man: offline-updates: make dependence on system-update.target explicitMichael Zhivich1-1/+1
Current operation of system-update-cleanup.service (removing /system-update symlink and rebooting) implies that any update must complete *before* system-update.target is reached. Update recommendations to include explicitly setting Before=system-update.target in services that use offline-updates mode. Signed-off-by: Michael Zhivich <mzhivich@akamai.com>
2019-07-12man: add example for setting multiple properties at onceLennart Poettering1-5/+9
Fixes: #4908
2019-07-12man: CPUShares= is so 2015Lennart Poettering1-1/+1
Let's update our example to the brave new cgroupsv2 world, and use CPUWeight= in our example.
2019-07-12man: document that WakeSystem= requires privsLennart Poettering1-7/+8
Fixes: #11677
2019-07-12man: document that "systemd-analyze blame/critical-chain" is not useful to ↵Lennart Poettering1-2/+13
track down job latency Fixes: #12272
2019-07-12man: be more explicit that Type=oneshot services are not "active" after startingLennart Poettering1-5/+11
Fixes: #13000
2019-07-12man: document that the supplementary groups list is initialized from User='s ↵Lennart Poettering1-1/+6
database entry Fixes: #12936
2019-07-12network: use string table to parse route table or scopeYu Watanabe1-2/+3
2019-07-12network: make Route.Type= support local, broadcast, anycast, multicast, nat, ↵Yu Watanabe1-1/+5
and xresolve Closes #12975.
2019-07-11Merge pull request #13017 from yuwata/network-neighbor-lladdr-13015Lennart Poettering1-2/+2
network: rename Neighbor.MACAddress= and also support IPv4 address
2019-07-11Merge pull request #12750 from keszybz/tmpfiles-c-copyLennart Poettering1-0/+31
Make tmpfiles C use --root
2019-07-11network: rename Neighbor.MACAddress= to Neighbor.LinkLayerAddress=Yu Watanabe1-2/+2
And make it support IPv4 address. Closes #13015.
2019-07-11man: document new "systemctl clean…" operationLennart Poettering4-10/+60
2019-07-11Merge pull request #13006 from yuwata/network-split-dhcp-12917Lennart Poettering1-13/+30
networkd: DHCPv6 - separate DHCPv6 options from DHCPv4 options
2019-07-11network: add AssignToLoopback= setting to [Tunnel] sectionYu Watanabe1-0/+7
networkd does not manage loopback interface lo. So, previously, we have no way to assign tunnel devices to lo.
2019-07-11Merge pull request #12755 from keszybz/short-identifiersLennart Poettering3-0/+21
Allow using unit names in status messages
2019-07-10Added support for xfrm interfaces18482-0/+74
2019-07-10Add config and kernel commandline option to use short identifiersZbigniew Jędrzejewski-Szmek3-0/+21
No functional change, just docs and configuration and parsing. v2: - change ShortIdentifiers=yes|no to StatusUnitFormat=name|description.
2019-07-10network: rename [DHCP] section to [DHCPv4]Yu Watanabe1-5/+5
To keep the backward compatibility broken by the previous commit.
2019-07-10networkd: DHCPv6 - separate DHCPv6 options from DHCPv4 optionsSusant Sahani1-9/+26
Closes https://github.com/systemd/systemd/issues/12917
2019-07-04man: Add some notes about variable $prefix for StateDirectory=Philip Withnall1-0/+9
tl;dr: It isn’t supported. Wording by Zbigniew Jędrzejewski-Szmek. See https://twitter.com/pid_eins/status/1102639279614906369 and https://gitlab.freedesktop.org/libfprint/fprintd/merge_requests/5#note_125536 onwards. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-07-03man: document tmpfiles.d/ user/group resolvability needsLennart Poettering1-0/+8
2019-07-02debug-generator: enable custom systemd.debug_shell ttyJan Synacek2-4/+9
2019-07-01man: fix wrong udev property nameYu Watanabe2-2/+2
2019-07-01network,udev: add Property= setting in [Match] sectionYu Watanabe2-0/+30
Closes #5665.
2019-06-30Merge pull request #12903 from keszybz/condition-quotingYu Watanabe1-4/+5
Condition quoting
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 20:36:33 +0000