summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* man: fix typoZbigniew Jędrzejewski-Szmek2022-05-161-1/+1
|
* man,mkosi: fedora 36 has been releasedZbigniew Jędrzejewski-Szmek2022-05-131-2/+2
|
* man: improve VtableExampleLuca Boccassi2022-05-111-9/+25
| | | | | | | | | | | | The methods published by the example have a reply in the signature, but the code was not sending any, so the client gets stuck waiting for a response that doesn't arrive. Echo back the input string. Update the object path to follow what would be the canonical format. Request a service name on the bus, so that the code can be dropped in a service and it can be dbus-activatable. It also makes it easier to see on busctl list.
* man: mention to Age parameter in C TypeKazuo Moriwaka2022-05-111-1/+3
|
* add missing cleanup-age to quickrefKazuo Moriwaka2022-05-101-6/+6
|
* core: annotate Reexecute() as NoReplyFrantisek Sumsal2022-05-101-0/+1
| | | | | So we're able to tell from the introspection data that the method doesn't reply.
* man: fix typoYu Watanabe2022-05-071-1/+1
|
* Merge pull request #23292 from alexhenrie/dhcpv6Yu Watanabe2022-05-071-10/+16
|\ | | | | network: clarify relationship between RA flags and DHCPv6 modes
| * network: clarify the relationship between DHCP= and WithoutRA=Alex Henrie2022-05-061-3/+4
| | | | | | | | | | Just setting DHCP=ipv6 is not enough to get DHCPv6 working without RA. The WithoutRA option must also be changed from its default of "no".
| * network: clarify the relationship between RA flags and DHCPv6 modesAlex Henrie2022-05-061-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the documentation, using the term "managed" for both the RA flag and the DHCPv6 mode is confusing because the mode is referred to as "solicit" both in the official DHCPv6 documentation (see RFC 8415) and in the WithoutRA option. Furthermore, calling the other RA flag "other information" or "other address configuration" is confusing because its official name is simply "other configuration" (see RFC 4861 and RFC 5175) and it isn't used to assign IP addresses. Rewrite the documentation for DHCPv6Client and WithoutRA to make it clear that getting the "managed" RA flag triggers the same kind of DHCP request as WithoutRA=solicit, whereas getting the "other configuration" RA flag triggers the same kind of DHCP request as WithoutRA=information-request.
* | Merge pull request #23272 from keszybz/logind-man-and-rulesYu Watanabe2022-05-0712-70/+39
|\ \ | |/ |/| Logind man and rules
| * man: deduplicate dbus versioning refZbigniew Jędrzejewski-Szmek2022-05-0512-67/+12
| |
| * man: beef up o.fd.login1 page a bit and recommend busctl tooZbigniew Jędrzejewski-Szmek2022-05-051-3/+27
| | | | | | | | gdbus is an external program, so it makes sense to recommend busctl.
* | Amend documentation for LimitNPROC=Jakob Lell2022-05-051-0/+8
| |
* | bootctl: add --quietZbigniew Jędrzejewski-Szmek2022-05-051-0/+8
| | | | | | | | | | It's useful for installation scripts and suchlike. Raised in https://bugzilla.redhat.com/show_bug.cgi?id=2079784#c9.
* | bootctl: support --graceful in is-installedZbigniew Jędrzejewski-Szmek2022-05-051-1/+2
| |
* | meson: Use meson test suite featureJan Janssen2022-05-041-0/+1
|/ | | | | | This makes it easier to only test a subset of tests without having to specify them all on the command line: meson test -C build --suite headers
* man/networkctl: mention initialized stateYu Watanabe2022-05-041-2/+8
| | | | Closes #23262.
* man: document that systemd-fstab-generator actually cares about ↵Lennart Poettering2022-05-021-0/+12
| | | | | | | | | roothash=/usrhash= on the kernel cmdline It doesn't really care about the hash value passed (which is processed by systemd-veritysetup-generator), but it does care about the fact that it is set (and mounts the DM nodes /dev/mapper/usr + /dev/mapper/root in that case).
* man: correct a major missed opportunityLennart Poettering2022-05-021-5/+7
| | | | | | | | | I don't know why this didn't occur to me earlier, but of course, it *has* to be this data. (This replaces some German prose about Berlin, that i guess only very few people will get. With the new blob I think we have a much broader chance of delivering smiles.)
* docs: Clarify where options are read fromDaan De Meyer2022-05-021-7/+8
| | | | | | Let's merge the footnote with the overall explanation of where systemd parses its options from and reword the section a bit to hopefully make things a bit more clear.
* Merge pull request #23170 from poettering/creds-copyLennart Poettering2022-05-024-13/+68
|\ | | | | import system credentials from sd-stub + qemu fw_cfg + kernel cmdline explicitly in PID 1
| * doc: add new markdown docs for credentialsLennart Poettering2022-04-283-2/+11
| |
| * man: document the new credentials featuresLennart Poettering2022-04-283-12/+58
| |
* | Merge pull request #23217 from keszybz/oomd-docsLennart Poettering2022-04-282-10/+31
|\ \ | |/ |/| More cross-references in bootctl/systemctl man pages
| * man: cross-advertize bootctl and systemctl boot loader supportZbigniew Jędrzejewski-Szmek2022-04-282-10/+31
| |
* | Merge pull request #23200 from keszybz/oomd-docsZbigniew Jędrzejewski-Szmek2022-04-283-54/+79
|\ \ | |/ | | Extend the documentation for oomd a bit
| * man: direct users to systemd-oomd if they read about OOMPolicyZbigniew Jędrzejewski-Szmek2022-04-281-2/+8
| | | | | | | | OOMPolicy remains valid, but let's push users for the userspace solution.
| * man: beef up the description of systemd-oomd.serviceZbigniew Jędrzejewski-Szmek2022-04-283-52/+71
| | | | | | | | | | | | | | | | | | | | | | | | The gist of the description is moved from systemd.resource-control to systemd-oomd man page. Cross-references to OOMPolicy, memory.oom.group, oomctl, ManagedOOMSwap and ManagedOOMMemoryPressure are added in all places. The descriptions are also more down-to-earth: instead of talking about "taking action" let's just say "kill". We *might* add configuration for different actions in the future, but we're not there yet, so let's just describe what we do now.
* | tree-wide: Fix typoYu Watanabe2022-04-251-1/+1
| |
* | cryptenroll,homectl: Introduce --fido2-credential-algorithm optionMkfsSion2022-04-222-0/+26
| | | | | | | | | | * Some authenticators(like Yubikey) support credential algorithm other than ES256 * Introduce a new option so users can make use of it
* | man: make clear that encrypted credentials are also authenticatedLennart Poettering2022-04-212-16/+17
|/ | | | | | We use authenticated encryption, and that deserves mention. This in particular relevant as the fact they are authenticated makes the credentials useful as initrd parameterization items.
* Merge pull request #23122 from poettering/creds-has-tpm2Lennart Poettering2022-04-201-0/+28
|\ | | | | tpm2: beef up tpm2 support checks
| * man: document new has-tpm2 verbLennart Poettering2022-04-201-0/+28
| |
* | man: update TPM2 PCR documentationLennart Poettering2022-04-202-7/+85
| | | | | | | | | | | | | | | | | | | | | | | | The assignments were partly simply incorrectly documented, partly changed with 4d32507f5186a89e98093659fbbe386787a97b9f and partly missing. Moreover kernel 5.17 now measures all initrds to PCR 9 on its own (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f046fff8bc4c4d8f8a478022e76e40b818f692df) Let's correct all this and bring it up-to-date. And while we are at it extend the docs about this in systemd-stub, with a new table that indicates which OS resource is protected by which PCR.
* | creds-util: permit credentials encrypted/signed by fixed zero length keys as ↵Lennart Poettering2022-04-201-11/+20
|/ | | | | | | | | | | | | | | | | fallback for systems lacking TPM2 This is supposed to be useful when generating credentials for immutable initrd environments, where it is is relevant to support credentials even on systems lacking a TPM2 chip. With this, if `systemd-creds encrypt --with-key=auto-initrd` is used a credential will be encrypted/signed with the TPM2 if it is available and recognized by the firmware. Otherwise it will be encrypted/signed with the fixed empty key, thus providing no confidentiality or authenticity. The idea is that distributions use this mode to generically create credentials that are as locked down as possible on the specific platform.
* hostnamed: display firmware versionSonali Srivastava2022-04-191-0/+6
|
* Merge pull request #23107 from yuwata/man-network-numeric-prefixYu Watanabe2022-04-183-32/+50
|\ | | | | man: recommend that .network or friends should have a numeric prefix
| * man: DHCPPrefixDelegation= needs to be enabled on downstream side for ↵Yu Watanabe2022-04-181-1/+1
| | | | | | | | | | | | assigning delegated prefixes Closes #23041.
| * man: recommend that .network or friends should have a numeric prefixYu Watanabe2022-04-183-31/+49
| | | | | | | | Closes #23105.
* | udevadm: info: also show parent devices by --treeYu Watanabe2022-04-171-1/+1
|/
* udevadm: add new --tree mode to "udevadm info"Lennart Poettering2022-04-131-0/+9
| | | | sysfs is a tree, hence let's a mode that allows showing it as such.
* man: document new generator env varsLennart Poettering2022-04-131-0/+60
|
* man: rebreak all paragraphs in systemd.generator(7)Lennart Poettering2022-04-131-113/+88
|
* man: add "internal" to "reference counter"Zbigniew Jędrzejewski-Szmek2022-04-124-21/+16
|
* man: add page for sd_device_{ref,unref,unrefp}Zbigniew Jędrzejewski-Szmek2022-04-124-8/+91
| | | | Gotta start somewhere.
* man: say libudev should not be used for new projectsZbigniew Jędrzejewski-Szmek2022-04-121-2/+4
|
* man: add landing page for sd-deviceZbigniew Jędrzejewski-Szmek2022-04-122-0/+62
| | | | | | We got documentation for sd-device for the first time with b51f4eaf7b58f064092215cea9c6fc1c5af5646e, so let's celebrate by adding a landing page that also explains the relationship with libudev.
* Fix man page linksZbigniew Jędrzejewski-Szmek2022-04-128-18/+19
| | | | Based on linkchecker as usual.
* Add comments about deprecated specifiersZbigniew Jędrzejewski-Szmek2022-04-111-0/+3
| | | | | Inspired by 9fe20c3234. When the specifier is undocumented, it is really easy to add a duplicate definition in a different place.
View Lorry Controller Status