summaryrefslogtreecommitdiffstats
path: root/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: lift pam_systemd_homed description to SummaryZbigniew Jędrzejewski-Szmek2022-07-131-10/+14
| | | | | | Also change the title to describe the module more comprehensively. Follow-up for 90bc309aa2c1430941f4c50f73e681ab3e488bd3. Suggested in https://bugzilla.redhat.com/show_bug.cgi?id=2085485#c5.
* Merge pull request #23881 from keszybz/kernel-install-strikes-yet-againYu Watanabe2022-07-131-76/+115
|\ | | | | kernel-install: fix invocation as installkernel, add tests, tweak documentation
| * kernel-install: allow overriding the plugin list tooZbigniew Jędrzejewski-Szmek2022-07-121-0/+5
| | | | | | | | | | The use of IFS=<newline> is dropped. Let's just iterate over the list, using any whitespace as separator.
| * kernel-install: allow overriding the path to config filesZbigniew Jędrzejewski-Szmek2022-07-061-7/+16
| | | | | | | | | | | | It's pretty hard to write tests without this. I started out by adding separate variables for each of the files we read, but there's a bunch, and in practice it's good enough to just override the directory.
| * man: rework documentation of kernel-install configZbigniew Jędrzejewski-Szmek2022-07-061-70/+95
| | | | | | | | | | | | | | Variables read by kernel-install and those exported by it were described without any clear separation. So in particular it was pretty hard to answer a question like "what variables can be set in install.conf". The in- and out-variables are now split into two separate subsections.
* | smack: Add DefaultSmackProcessLabel to user.conf and system.confŁukasz Stelmach2022-07-121-0/+12
| | | | | | | | | | | | | | | | | | | | | | DefaultSmackProcessLabel tells systemd what label to assign to its child process in case SmackProcessLabel is not set in the service file. By default, when DefaultSmackProcessLabel is not set child processes inherit label from systemd. If DefaultSmackProcessLabel is set to "/" (which is an invalid character for a SMACK label) the DEFAULT_SMACK_PROCESS_LABEL set during compilation is ignored and systemd act as if the option was unset.
* | Merge pull request #23979 from DaanDeMeyer/nspawn-relative-pathsLuca Boccassi2022-07-121-26/+20
|\ \ | | | | | | nspawn: Support relative paths for --bind and --overlay
| * | nspawn: Support relative source paths for --bind and --overlayDaan De Meyer2022-07-121-2/+4
| | |
| * | nspawn: Rewrap --overlay docsDaan De Meyer2022-07-111-25/+17
| | |
* | | man: explain why pam_systemd_home wants to be in all four stacksLennart Poettering2022-07-111-2/+7
|/ / | | | | | | | | | | Suggested here: https://bugzilla.redhat.com/show_bug.cgi?id=2085485#c5
* | manager: add taint flag "support-ended"Zbigniew Jędrzejewski-Szmek2022-07-101-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | In the welcome line, use NAME= as the fallback for PRETTY_NAME=. PRETTY_NAME= doesn't have to be set, but NAME= should. Example output: --- Welcome to Fedora Linux 37 (Rawhide Prerelease)! [ !! ] This OS version (Fedora Linux 37 (Rawhide Prerelease)) is past its end-of-support date (1999-01-01) Queued start job for default target graphical.target. [ OK ] Created slice system-getty.slice. ---
* | man: update the description of taint flagsZbigniew Jędrzejewski-Szmek2022-07-091-15/+81
| | | | | | | | | | | | We had a description in README, and an outdated list in the man page. I think we should keep a reference-style list in the man page. The description in README is more free-form.
* | man: redefine SUPPORT_END= to mean one day earlierZbigniew Jędrzejewski-Szmek2022-07-091-3/+6
| | | | | | | | | | | | | | | | | | | | I thought it would be nice to specify the last day of support, because I thought it'd seem more natural. But in practice this doesn't work well, because such a truncated timestamp is usually taken to mean midnight that starts the given date. I.e. 2011-12-13 is a shorthand for 2011-12-13 00:00:00 and not 2011-12-13 23:59:59.999999999999. Let's instead specify that the given date is the first unsupported day, which is meaningful for humans, and let the computer treat it as midnight, which gives consistent interpratation.
* | Merge pull request #23731 from bluca/bootctl_imageLuca Boccassi2022-07-081-0/+31
|\ \ | | | | | | bootctl: add --root and --image
| * | bootctl: add --install-source=auto|image|hostLuca Boccassi2022-07-081-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | When using --root=/--image= the binaries to install/update will be picked from the directory/image. Add an option to let the caller choose. By default (auto) the image is tried first, and if nothing is found then the host. The other options allow to strictly try the image or host and ignore the other.
| * | bootctl: add --root and --imageLuca Boccassi2022-07-081-0/+21
| | | | | | | | | | | | Operate on image/directory, and also take files to install from it
* | | resolvectl man page: Word correctionFrank Dana2022-07-071-1/+1
|/ /
* | os-release: define SUPPORT_END=Zbigniew Jędrzejewski-Szmek2022-07-071-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #21764. I think is very simple, but flexible. The date may be set early, for distros that have a fixed schedule, but it doesn't have to. So for example Debian could push out an update that sets a few months before the release goes EOL. And various tools, in particular graphical desktops, can start nagging people to upgrade a few weeks before the date. As discussed in the bug, we don't need granularity higher than a day. And this means that we can use a simple human- and machine-readable format. I was considering other names, e.g. something with "EOL", but I think that "SUPPORT_END" is better because it doesn't imply that the machine will somehow stop working. This is supposed to be an advisory, nothing more.
* | Merge pull request #15205 from jlebon/pr/preset-all-firstbootZbigniew Jędrzejewski-Szmek2022-07-061-1/+1
|\ \ | | | | | | manager: optionally, do a full preset on first boot
| * | systemctl: stop saying "vendor preset"Zbigniew Jędrzejewski-Szmek2022-05-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have vendor presets, and local admin presets, and runtime presets (under /usr/lib, /usr/local/lib and /etc, /run, respectively). When we display preset state, it can be configured in any of those places, so we shouldn't say anything about the origin. (Another nice advantage is that it improves alignment: [root@f36 ~]# systemctl list-unit-files multipathd.service UNIT FILE STATE VENDOR PRESET multipathd.service enabled enabled ^ this looks we have a "PRESET" column that is empty.)
* | | man: "enabled commands are started at boot" is rubbishLennart Poettering2022-07-061-20/+22
| | | | | | | | | | | | | | | | | | | | | it's enabled units, and they might be started by various forms of activation, not just "at boot". Fix that.
* | | Merge pull request #23916 from keszybz/assorted-patchesYu Watanabe2022-07-061-3/+3
|\ \ \ | | | | | | | | Assorted patches
| * | | man: fix link to glob(3)Zbigniew Jędrzejewski-Szmek2022-07-051-3/+3
| | | |
* | | | docs: normalize uppercasing of titles of network docLennart Poettering2022-07-051-22/+16
| | | |
* | | | tree-wide: link to docs.kernel.org for kernel documentationnl67202022-07-0419-55/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | https://www.kernel.org/ links to https://docs.kernel.org/ for the documentation. See https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=ebc1c372850f249dd143c6d942e66c88ec610520 These URLs are shorter and nicer looking.
* | | | man/network: fix wording and syntaxZbigniew Jędrzejewski-Szmek2022-07-021-5/+5
| | | | | | | | | | | | | | | | | | | | Follow-up for 0bcc6557fbba32ebcdf323e76688ced50e3c8d8e. Docbook doesn't know <variable>.
* | | | tree-wide: use html links for kernel docsZbigniew Jędrzejewski-Szmek2022-07-0211-33/+28
|/ / / | | | | | | | | | Instead of using "*.txt" as reference name, use the actual destination title.
* | | sd-bus: use assert_return() in public function sd_bus_message_dumpZbigniew Jędrzejewski-Szmek2022-06-301-3/+4
| | | | | | | | | | | | Also, document that NULL is allowed.
* | | sd-event: let sd_event_source_set_enabled accept NULLZbigniew Jędrzejewski-Szmek2022-06-301-10/+9
| | | | | | | | | | | | | | | | | | Same story as before: disabling a non-existent event source shouldn't need to be guarded by an if. I retained the wrapper so that that we don't have to say SD_EVENT_OFF in the many places where this is called.
* | | sd-event: allow sd_event_source_is_enabled() to return false for NULLZbigniew Jędrzejewski-Szmek2022-06-301-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a natural use case, and instead of defining a wrapper to do this for us, let's just make this part of the API. Calling with NULL was not allowed, so this is not a breaking change to the interface. (After sd_event_source_is_enabled was originally added, we introduced sd_event_source_disable_unref() and other similar functions which accept NULL. So not accepting NULL here is likely to confuse people. Let's just make the API usable with minimal fuss.)
* | | man: document sd_bus_message_read_strv_extend()Zbigniew Jędrzejewski-Szmek2022-06-302-5/+19
| | |
* | | man: document sd_id128_string_equal()Zbigniew Jędrzejewski-Szmek2022-06-302-0/+12
| | |
* | | man: rework the text in sd-id128Zbigniew Jędrzejewski-Szmek2022-06-301-45/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In places the text was overly formal, e.g. "an 128-bit ID" was repeated, even though it is clear from the context that we're talking about this type of ID. OTOH, in other places the text was informal, e.g. "You can use …". Also, "you may use f() to frob" → "f() frobs". The text without all the flourishes is easier to read. sd_id128_in_set_sentinel() was described only in passing when taking about sd_id128_in_set(), now it gets is own brief paragraph. The synopsis was missing.
* | | man: document sd_bus_error_setfv()Zbigniew Jędrzejewski-Szmek2022-06-302-17/+29
| | | | | | | | | | | | | | | The description for sd_bus_error_set_errnof/sd_bus_error_set_errnofv are adjusted to use the same pattern.
* | | meson: update man-generation rules for sd_hwdb_new_from_pathZbigniew Jędrzejewski-Szmek2022-06-301-1/+4
| |/ |/| | | | | Forgotten in 60f0ba75569312825ff14680d05a4b4f95842951.
* | Use https for man7.orgMichael Biebl2022-06-282-2/+2
| |
* | Use https for freedesktop.orgMichael Biebl2022-06-2819-26/+26
| | | | | | | | grep -l -r http:// | xargs sed -E -i s'#http://(.*).freedesktop.org#https://\1.freedesktop.org#'
* | logind-session-dbus: allow to set display name via dbusDavid Tardon2022-06-221-0/+8
| | | | | | | | | | | | | | | | Currently, the only way to set display name of a graphical session is to pass it to CreateSession(). But modern display managers like gdm start the display server as part of the user session, which means that the display name isn't known yet when the session is being created. Hence, let's make it possible to set it later.
* | Merge pull request #23774 from yuwata/netlabel-nftset-follow-upsYu Watanabe2022-06-224-241/+0
|\ \ | | | | | | network, core: revert NFTSet and NetLabel features
| * | Revert "networkd: NetLabel integration"Yu Watanabe2022-06-221-54/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts PR #23269 and its follow-up commit. Especially, 2299b1cae32c1fb8911da0ce26efced68032f4f8 (partially), and 3cf63830acdef9d8afdc9ef1cf25aa7e85a5e4d5. The PR was merged without final approval, and has several issues: - The NetLabel for static addresses are not assigned, as labels are stored in the Address objects managed by Network, instead of Link. - If NetLabel is specified for a static address, then the address section will be invalid and the address will not be configured, - It should be implemented with Request object, - There is no test about the feature.
| * | Revert NFTSet featureYu Watanabe2022-06-224-187/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts PR #22587 and its follow-up commit. More specifically, 2299b1cae32c1fb8911da0ce26efced68032f4f8 (partially), e176f855278d5098d3fecc5aa24ba702147d42e0, ceb46a31a01b3d3d1d6095d857e29ea214a2776b, and 51bb9076ab8c050bebb64db5035852385accda35. The PR was merged without final approval, and has several issues: - OSS fuzz reported issues in the conf parser, - It calls synchrnous netlink call, it should not be especially in PID1, - The importance of NFTSet for CGroup and DynamicUser may be questionable, at least, there was no justification PID1 should support it. - For networkd, it should be implemented with Request object, - There is no test for the feature. Fixes #23711. Fixes #23717. Fixes #23719. Fixes #23720. Fixes #23721. Fixes #23759.
* | | Merge pull request #23806 from keszybz/udevadm-info-pagerZbigniew Jędrzejewski-Szmek2022-06-221-0/+1
|\ \ \ | |/ / |/| | Pager for udevadm info
| * | udevadm info: implement --no-pagerZbigniew Jędrzejewski-Szmek2022-06-221-0/+1
| | |
* | | cryptenroll: fix typo in manpageFoster Snowhill2022-06-181-1/+1
| | |
* | | tree-wide: fix typoYu Watanabe2022-06-151-1/+1
| | |
* | | man: Add some punctuation; remove double spaces.adrian52022-06-141-40/+40
|/ /
* | boot: Drop use of MetaiMatchJan Janssen2022-06-091-1/+8
| | | | | | | | | | | | | | | | A future commit will add support for unicode collation protocol that allows case folding and comparing strings with locale awareness. But it only operates on whole strings, so fnmatch cannot use those without a heavy cost. Instead we just case fold the patterns instead (the IDs we try to match are already lower case).
* | core: firewall integration with DynamicUserNFTSet=Topi Miettinen2022-06-082-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New directive `DynamicUserNFTSet=` provides a method for integrating configuration of dynamic users into firewall rules with NFT sets. Example: ``` table inet filter { set u { typeof meta skuid } chain service_output { meta skuid != @u drop accept } } ``` ``` /etc/systemd/system/dunft.service [Service] DynamicUser=yes DynamicUserNFTSet=inet:filter:u ExecStart=/bin/sleep 1000 [Install] WantedBy=multi-user.target ``` ``` $ sudo nft list set inet filter u table inet filter { set u { typeof meta skuid elements = { 64864 } } } $ ps -n --format user,group,pid,command -p `pgrep sleep` USER GROUP PID COMMAND 64864 64864 55158 /bin/sleep 1000 ```
* | core: firewall integration with ControlGroupNFTSet=Topi Miettinen2022-06-082-0/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New directive `ControlGroupNFTSet=` provides a method for integrating services into firewall rules with NFT sets. Example: ``` table inet filter { ... set timesyncd { type cgroupsv2 } chain ntp_output { socket cgroupv2 != @timesyncd counter drop accept } ... } ``` /etc/systemd/system/systemd-timesyncd.service.d/override.conf ``` [Service] ControlGroupNFTSet=inet:filter:timesyncd ``` ``` $ sudo nft list set inet filter timesyncd table inet filter { set timesyncd { type cgroupsv2 elements = { "system.slice/systemd-timesyncd.service" } } } ```
* | network: firewall integration with NFT setsTopi Miettinen2022-06-081-0/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New directives `NFTSet=`, `IPv4NFTSet=` and `IPv6NFTSet=` provide a method for integrating configuration of dynamic networks into firewall rules with NFT sets. /etc/systemd/network/eth.network ``` [DHCPv4] ... NFTSet=netdev:filter:eth_ipv4_address ``` ``` table netdev filter { set eth_ipv4_address { type ipv4_addr flags interval } chain eth_ingress { type filter hook ingress device "eth0" priority filter; policy drop; ip saddr != @eth_ipv4_address drop accept } } ``` ``` sudo nft list set netdev filter eth_ipv4_address table netdev filter { set eth_ipv4_address { type ipv4_addr flags interval elements = { 10.0.0.0/24 } } } ```
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 07:04:03 +0100