summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* network: clean-up DHCP lease server data configurationLennart Poettering2020-06-181-72/+29
| | | | | | | | | | | | | | | | | | | | | | | | This is an attempt to clean up the POP3/SMTP/LPR/… DHCP lease server data logic in networkd. This reduces code duplication and fixes a number of bugs. This removes any support for collecting POP3/SMPT/LPR servers acquired via local DHCP client releases since noone uses that, and given how old these protocols are I doubt this will change. It keeps support for configuring them for the dhcp server however. The differences between the DNS/NTP/SIP/POP3/SMTP/LPR configuration logics are minimized. This removes the relevant symbols from sd-network.h (which is an internal API only at this point after all). This is unfortunately not well test, given the old code for this had barely any tests. But the new code should not perform worse at least, and allow us to release, since it corrects some interfaces visible in the .network configuration format. Fixes: #15943
* network: DHCPv6 - Add support to set token on the LAN interfaceSusant Sahani2020-06-171-0/+10
| | | | | This patch adds support to set a token on the LAN interface for the acquired delegated prefixes for the DHCPv6 to generate address.
* Merge pull request #16170 from keszybz/man-user@Zbigniew Jędrzejewski-Szmek2020-06-143-15/+21
|\ | | | | Better documentation for user@ services
| * man: mention systemd-user-runtime-dir in user@.service tooZbigniew Jędrzejewski-Szmek2020-06-142-13/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | _riotingpacifist was complaining on reddit [1] that systemd-user-runtime-dir is not documented anywhere. So let's add the binary name as page alias. [1] https://www.reddit.com/r/linux/comments/h086fd/why_linuxs_systemd_is_still_divisive_after_all/ftllr66/ This page should be in section 8, like all .service descriptions. Also extend the text a bit to make it clearer that systemd --user is the same executable but running in a different mode (which might be certainly a bit confusing to users.)
| * man: really fix conditional in homed.confZbigniew Jędrzejewski-Szmek2020-06-131-1/+1
| | | | | | | | Followup for f978844eb62e1c47431b388ab90aafdd29f624ec.
| * man: drop obsolete HAVE_PYTHON conditionalZbigniew Jędrzejewski-Szmek2020-06-131-1/+1
| | | | | | | | | | | | It stopped making sense when automake support was dropped and python started being required to perform a build. Follow-up for 72cdb3e783174dcf9223a49f03e3b0e2ca95ddb8.
* | man: Document the crypttab keyfile syntax specifying a deviceVladimir Panteleev2020-06-141-7/+9
|/ | | | | | Feature introduced in 50d2eba27b9bfc77ef6b40e5721713846815418b. Also documented as part of the kernel parameter syntax in systemd-cryptsetup-generator(8), but should also be documented here as part of the overall file syntax.
* Merge pull request #16046 from bluca/dissect_squashfs_verityLennart Poettering2020-06-091-2/+18
|\ | | | | dissect: single-filesystem verity images with external hashdevice
| * dissect: support single-filesystem verity images with external verity hashLuca Boccassi2020-06-091-2/+18
| | | | | | | | | | | | | | | | dm-verity support in dissect-image at the moment is restricted to GPT volumes. If the image a single-filesystem type without a partition table (eg: squashfs) and a roothash/verity file are passed, set the verity flag and mark as read-only.
* | man: udevadm: mention non-zero exit code on settleYigal Korman2020-06-091-1/+3
| | | | | | | | | | 'udevadm settle --timeout=XY' will return 1 in case the timeout was reached and the event queue was not empty. The manpage should mention it.
* | doc: Try to clarify automount dependency confusionChris Down2020-06-091-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Arch recently upgraded systemd to 245.6. Shortly afterwards, users began reporting[0] that systemd detected an ordering cycle, and they were unable to log in. The reason they were unable to log in was because of ordering cycle resolution: [...] systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start systemd[1]: sysinit.target: Job systemd-update-done.service/start deleted to break ordering cycle starting with sysinit.target/start systemd[1]: sysinit.target: Job systemd-journal-catalog-update.service/start deleted to break ordering cycle starting with sysinit.target/start systemd[1]: sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start [...] Whether the resolution did the right thing here or not is a longer-term discussion, but in the interim we should at least make this distinction between automount dependencies and mount dependencies clearer in the documentation, so that users and distribution maintainers know what's acceptable. In this case Arch actually backed out b3d7aef5 entirely and released a new version due to the confusion. Also see https://github.com/systemd/systemd-stable/issues/69. 0: https://bugs.archlinux.org/task/66908
* | core: let user define start-/stop-timeout behaviourJan Klötzke2020-06-091-11/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The usual behaviour when a timeout expires is to terminate/kill the service. This is what user usually want in production systems. To debug services that fail to start/stop (especially sporadic failures) it might be necessary to trigger the watchdog machinery and write core dumps, though. Likewise, it is usually just a waste of time to gracefully stop a stuck service. Instead it might save time to go directly into kill mode. This commit adds two new options to services: TimeoutStartFailureMode= and TimeoutStopFailureMode=. Both take the same values and tweak the behavior of systemd when a start/stop timeout expires: * 'terminate': is the default behaviour as it has always been, * 'abort': triggers the watchdog machinery and will send SIGABRT (unless WatchdogSignal was changed) and * 'kill' will directly send SIGKILL. To handle the stop failure mode in stop-post state too a new final-watchdog state needs to be introduced.
* | Merge pull request #16047 from poettering/udev-ro-blockLennart Poettering2020-06-092-7/+24
|\ \ | | | | | | udev: optionally mark all block devices popping up read-only by default
| * | man: single-char parameters take no '='Lennart Poettering2020-06-081-4/+4
| | | | | | | | | | | | The suggested syntax is simply not valid and results in an error.
| * | udev: optionally mark all block devices read-only as they pop upLennart Poettering2020-06-082-3/+20
| |/
* | Add 'bitlk' option to mount Bitlocker drives with cryptsetup.Maxim Fomin2020-06-091-0/+7
| |
* | network: introduce IPv4AcceptLocal= settingYu Watanabe2020-06-081-0/+7
|/ | | | Closes #16090.
* man: fix typo Takse -> TakesSusant Sahani2020-06-061-1/+1
|
* Merge pull request #15378 from msekletar/udev-kill-signalZbigniew Jędrzejewski-Szmek2020-06-053-0/+37
|\ | | | | udev: make signal that we use to kill workers on timeout configurable
| * udev: make signal that we use to kill workers on timeout configurableMichal Sekletár2020-06-053-0/+37
| |
* | Merge pull request #15171 from ssahani/tc-qfqYu Watanabe2020-06-041-0/+39
|\ \ | | | | | | network: TC- Introduce Quick Fair Queueing (QFQ)
| * | network: tc: introduce [QuickFairQueueingClass] sectionYu Watanabe2020-06-031-0/+28
| | |
| * | network: tc: introduce Quick Fair Queueing (QFQ)Susant Sahani2020-06-031-0/+11
| | |
* | | Merge pull request #16056 from keszybz/minor-doc-updatesLennart Poettering2020-06-032-10/+13
|\ \ \ | | | | | | | | Minor doc updates
| * | | man: add note that emergency.target inherits mount stateZbigniew Jędrzejewski-Szmek2020-06-021-8/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Based on an internal discussion whether emergency.target should remount disks ro, or maybe remount them rw, or do nothing. In some cases people want to boot ro, and always remounting rw would break that. In other cases, remounting disks ro after they have already been mounted rw is mostly pointless and might even not be possible. So let's just document that we don't change the state. Also: any→other, since emergency.service *is* pulled in. Also: just advertise "emergency" as the way to boot into the target. We are not going to remove this option, and it's way easier to type than "systemd.unit=emergency.target".
| * | | man,mkosi: bump Fedora versionZbigniew Jędrzejewski-Szmek2020-06-021-2/+2
| | |/ | |/|
* | | core: remove support for ".include" stanzaLennart Poettering2020-06-031-3/+0
| |/ |/| | | | | | | | | | | | | | | | | Six years ago we declared it obsolete and removed it from the docs (c073a0c4a5ffbf6677dd6af02e7c7d59b2b901ab) and added a note about it in NEWS. Two years ago we add warning messages about it, indicating the feature will be removed (41b283d0f1f4abd85d0bbeeb7f71bb30f87cfab9) and mentioned it in NEWS again. Let's now kill it for good.
* | network: add DHCPv6.RouteMetric=Yu Watanabe2020-06-021-2/+8
|/ | | | Hopefully fixes #15295.
* Merge pull request #15884 from ssahani/dhcpv6-vendorYu Watanabe2020-06-011-0/+16
|\ | | | | DHCPv6: Introduce vendor specific
| * network: Inroduce DHCP6- send vendor optionsSusant Sahani2020-05-291-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | network: Inroduce DHCP6- send vendor options ``` 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_VENDOR_OPTS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | enterprise-number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . vendor-option-data . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | sub-opt-code | sub-option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . sub-option-data . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 31: Vendor-specific Options Format sub-opt-code The code for the sub-option. A 2-octet field. sub-option-len An unsigned integer giving the length of the sub-option-data field in this sub-option in octets. A 2-octet field. sub-option-data The data area for the sub-option. The length, in octets, is specified by sub-option-len. ```
* | Merge pull request #15935 from poettering/cache-more-efi-varsZbigniew Jędrzejewski-Szmek2020-05-301-1/+12
|\ \ | | | | | | logind + efi-loader: cache more efi vars
| * | bootctl: add simple, low-level reboot-to-firmware verb for controlling the flagLennart Poettering2020-05-291-1/+12
| |/
* | Merge pull request #15915 from poettering/journal-external-linkZbigniew Jędrzejewski-Szmek2020-05-301-0/+10
|\ \ | | | | | | journal: show external links in log output
| * | man: briefly document the DOCUMENTATION= structure log fieldLennart Poettering2020-05-291-0/+10
| |/
* | Merge pull request #15958 from layderv/masterDaan De Meyer2020-05-301-5/+13
|\ \ | | | | | | #15773 add --reboot-arg to systemctl reboot
| * | #15773 add --reboot-argument to systemctl rebootlaydervus2020-05-291-5/+13
| |/
* | Fix typo.Michael Gubbels2020-05-291-1/+1
|/
* network: DHCPv6 Assign delegated prefix to LAN interfaceSusant Sahani2020-05-291-1/+13
| | | | | | | | | In DHCPv6-PD environment, where WAN interface requests IPv6 via DHCPv6, receives the address as well as delegated prefixes, with LAN interfaces serving those delegated prefixes in their router advertisement messages. The LAN interfaces on the router themselves do not have the IPv6 addresses assigned by networkd from the prefix it serves on that interface. Now this patch enables it.
* Merge pull request #15944 from poettering/sd-path-fixupsYu Watanabe2020-05-291-24/+24
|\ | | | | sd-path: some fixups
| * sd-path: drop "-dir" and "-path" suffixes from path enumsLennart Poettering2020-05-281-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clean up the naming of the sd-path enums. Previously, the more recently added fields where named in the form SD_PATH_xyz_DIR and SD_PATH_xyz_PATH, while the older fields where called just SD_PATH_xyz and SD_PATH_SEARCH_xyz. Let's clean this up, to come to a more unified way how we name this stuff. I opted to stick to the old naming, i.e. dropthe suffixes. It's a bit of a bike-shedding question of course, but I think there's a good reason to avoid the additional DIR and PATH suffixes: the enum prefix contains "PATH" anyway (i.e. "SD_PATH_"), so including PATH twice in each name is redundant. Moreover, the key difference between the enums with the "dir" and the "path" in the name is that the latter are *seach* paths, and I think this is better emphasized by sticking to the "SEARCH" in the name. Moreover dropping the suffixes makes the identifiers a lot shorter, in particular in the "systemd-path" list output. And that's always good. This means the naming pkgconfig file and in sd-path slightly deviate (though the mapping is very simple), but I think that's OK, given that this is developer facing and not user facing.
* | Merge pull request #15942 from poettering/pass-pktinfoYu Watanabe2020-05-291-0/+9
|\ \ | | | | | | disable PassCredentials= on networkd netlink socket, enable NETLINK_PKTINFO instead
| * | core: add new PassPacketInfo= socket unit propertyLennart Poettering2020-05-271-0/+9
| | |
* | | Merge pull request #15619 from ddstreet/ignore_carrier_loss_defaultYu Watanabe2020-05-291-3/+5
|\ \ \ | |_|/ |/| | Set IgnoreCarrierLoss= default to value of ConfigureWithoutCarrier=
| * | network: Change IgnoreCarrierLoss default to value of ConfigureWithoutCarrierDan Streetman2020-05-261-3/+5
| | | | | | | | | | | | | | | | | | It doesn't make much sense to have ConfigureWithoutCarrier set, but not IgnoreCarrierLoss; all the configuration added during initial interface bring-up will be lost at the first carrier up/down.
* | | firstboot: Add --kernel-command-line optionDaan De Meyer2020-05-271-0/+9
| | |
* | | firstboot: Add --root-password-hashed optionDaan De Meyer2020-05-271-10/+10
| | |
* | | firstboot: Add --delete-root-password optionDaan De Meyer2020-05-271-0/+8
| | |
* | | firstboot: Add --force optionDaan De Meyer2020-05-271-0/+9
| |/ |/|
* | Merge pull request #15669 from andir/systemd-ipv6-pd-subnet-idLennart Poettering2020-05-271-0/+10
|\ \ | | | | | | networkd: subnet id support for ipv6 prefix delegation
| * | networkd: Add support for setting a preferred subnet id for IPv6 PD leasesAndreas Rammhold2020-05-261-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows users to configure a subnet id that should be used instead of automatically (sequentially) assigned subnets. The previous attempt had the downside that the subnet id would not be the same between networkd restarts. In some setups it is desirable to have predictable subnet ids across restarts of services and systems. The code for the assignment had to be broken up into two pieces. One of them is the old (sequential) assignment of prefixes and the other is the new assignment based on configured subnet ids. The new assignment code has to be executed first and has to be taken into account when (later on) allocating the "old" subnets from the same pool. Instead of having one iteration through the links we are now trying to allocate a prefix for every link on every delegated prefix, unless they received an assignment in a previous iteration.
View Lorry Controller Status