summaryrefslogtreecommitdiffstats
path: root/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: document SystemState's possible valuesLuca Boccassi2023-09-251-2/+46
|
* man: add version information for udev functionsAbderrahim Kitouni2023-09-2511-0/+111
|
* Merge pull request #29314 from YHNdnzj/firstboot-fixupLuca Boccassi2023-09-251-1/+1
|\ | | | | Small fixups for first boot
| * man/systemd-firstboot: /etc/ empty -> unpopulatedMike Yuan2023-09-251-1/+1
| | | | | | | | | | We use the phrase "unpopulated" in systemd.unit(5) too. And "/etc/ is empty" is simply spurious.
* | Merge pull request #29308 from aafeijoo-suse/dissect-fixLuca Boccassi2023-09-251-1/+6
|\ \ | |/ |/| dissect: fix man and bash-completion
| * man/systemd-dissect: various fixesAntonio Alvarez Feijoo2023-09-251-1/+6
| | | | | | | | | | - Add synopsis to `--discover` and `--validate` options. - `-l` is for `--list`, not for `--mtree`.
* | man: briefly document that we are now keeping an event log in userspace for ↵Lennart Poettering2023-09-251-0/+24
| | | | | | | | out measurements
* | pcrextend: make PCR index configurableLennart Poettering2023-09-251-0/+9
| | | | | | | | | | Let's make the tool a tiny bit more generic by allowing the PCR index to measure into to be configurable.
* | pcrphase: rename binary to pcrextendLennart Poettering2023-09-253-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tool initially just measured the boot phase, but was subsequently extended to measure file system and machine IDs, too. At AllSystemsGo there were request to add more, and make the tool generically accessible. Hence, let's rename the binary (but not the pcrphase services), to make clear the tool is not just measureing the boot phase, but a lot of other things too. The tool is located in /usr/lib/ and still relatively new, hence let's just rename the binary and be done with it, while keeping the unit names stable. While we are at it, also move the tool out of src/boot/ and into its own src/pcrextend/ dir, since it's not really doing boot related stuff anymore.
* | man: fix docbook syntax for function docsAbderrahim Kitouni2023-09-252-14/+9
| | | | | | | | This fixes sd_bus_error_add_map and man/sd_uid_get_state
* | man/kernel-command-line: don't refer early_core_pattern to systemdAbderrahim Kitouni2023-09-251-1/+0
|/ | | | It is defined later in the same file
* Add recommended initramfs regenerationRoepLuke2023-09-223-0/+27
| | | | | | | | | I recently tried adding a FIDO2-Device as an unlocking method to the LUKS2 partition containing my Fedora install. When trying to do this, I stumbled upon the here edited man files detailing how to do this. I however could not unlock my partition with my FIDO2-Device after editing /etc/crypttab and rebooting. As I found out after a while, I needed to regenerate / update my currently running / used initramfs (https://unix.stackexchange.com/a/705809). This would have most likely solved itself for me with the next kernel update install (as far as I understand). So I propose changing the files edited here to recommend or at least inform the user about this.
* treewide: split commandline into command lineJoerg Behrmann2023-09-204-12/+12
|
* docs: excorcise NIS from nsswitch.confLennart Poettering2023-09-204-17/+16
| | | | | | | | | | | | | | | | Let's replace the "compat" module in our proposed nsswitch.conf configuration with "files", since it is not 1995 anymore. Fedora and other distros have deprecated and removed NIS support a while back. While others still retain some support I am not sure we should advertise it in our examples. Downstream can of course still use "compat" instead of "files" if they want to, but let's not confuse people who don't care about NIS anymore with this. Also, bring the nsswitch.conf snippet in README in line with what our man pages say. Also see: https://fedoraproject.org/wiki/Changes/retire_NIS_user_space_utils
* man/kernel-install: document missing $KERNEL_INSTALL_IMAGE_TYPEAntonio Alvarez Feijoo2023-09-201-0/+30
| | | | Available since https://github.com/systemd/systemd/commit/3d5f0bfe
* Merge pull request #28919 from fbuihuu/custom-config-file-install-pathZbigniew Jędrzejewski-Szmek2023-09-201-6/+9
|\ | | | | Custom config file install path
| * Reflect the fact that main config files can be installed in /usrFranck Bui2023-09-191-6/+9
| |
* | Merge pull request #29150 from abderrahim/version-info-dbusLuca Boccassi2023-09-197-0/+242
|\ \ | |/ |/| man: add version information for dbus interfaces
| * man: add version information for dbus interfacesAbderrahim Kitouni2023-09-197-0/+242
| | | | | | | | | | These only go back to version 250 which is the first version to provide the export-dbus-interfaces build target.
* | Merge pull request #29221 from keszybz/fedora-cloud-latestDaan De Meyer2023-09-191-2/+2
|\ \ | |/ |/| man: update Fedora release information
| * man: update Fedora release informationZbigniew Jędrzejewski-Szmek2023-09-191-2/+2
| |
* | man: condense version information for functionsAbderrahim Kitouni2023-09-19100-447/+448
| | | | | | | | Use a more compact form like 'a, b, and c were added in version x'
* | man: remove quotes around default valuesJoerg Behrmann2023-09-192-4/+4
| |
* | treewide: fix typosJoerg Behrmann2023-09-193-4/+4
| | | | | | | | | | | | - mostly: usecase -> use case - continously -> continuously - single typos in docs/FILE_DESCRIPTOR_STORE.md
* | Merge pull request #29159 from poettering/socket-pauseLennart Poettering2023-09-192-11/+59
|\ \ | |/ |/| core: add new "PollLimit" settings to .socket units
| * man: document the new PollLimitIntervalSec=/PollLimitBurst= settingsLennart Poettering2023-09-181-11/+47
| |
| * core: add new "PollLimit" settings to .socket unitsLennart Poettering2023-09-181-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a new "PollLimit" pair of settings to .socket units, very similar to existing "TriggerLimit" logic. The differences are: * PollLimit focusses on the polling on the sockets, and pauses that temporarily if a ratelimit on that is reached. TriggerLimit otoh focusses on the triggering effect of socket units, and stops triggering once the ratelimit is hit. * While the trigger limit being hit is an action that causes the socket unit to fail the polling limit being reached will just temporarily disable polling on the socket fd, and it is resumed once the ratelimit interval is over. * When a socket unit operates on multiple socket fds (e,g, ListenStream= on both some ipv6 and an ipv4 address or so). Then the PollLimit will be specific to each fd, while the trigger limit is specific to the whole unit. Implementation-wise this is mostly a wrapper around sd-event's sd_event_source_set_ratelimit(), which exposes the desired behaviour directly. Usecase for all of this: socket services which when overloaded with connections should just slow down reception of it, but not fail persistently.
* | systemd.time.7: rewrite Parsing Timestamps sectionнаб2023-09-191-24/+38
| |
* | man: update version informationAbderrahim Kitouni2023-09-1969-447/+1577
| | | | | | | | | | | | | | | | As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
* | Merge pull request #29186 from keszybz/man-notifications-and-fd-storeLuca Boccassi2023-09-194-279/+294
|\ \ | |/ |/| man: notifications and fd store
| * man/daemon: s/init system/service manager/Zbigniew Jędrzejewski-Szmek2023-09-181-133/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | As pointed out in the review, all this applies to the user services too, so are not managed by the "init system", but by the more generic "service manager". Also: - use oxford comma - change "employ" to "use" in various places - change "the init system forwards messages to syslog" to "are forwarded to syslog". This is done by systemd-journald, so really there is no forwarding, because systemd-journald just writes them to a file in the common setup, so let's use the passive form to avoid specifying who does this.
| * man/daemon: recommend status notications, mention fd storeZbigniew Jędrzejewski-Szmek2023-09-151-11/+23
| | | | | | | | | | This is just a small update. We probably should write a much longer document that describes how to write a daemon in the XXI century.
| * man/sd_notify: change recommendations about unsupported notificationsZbigniew Jędrzejewski-Szmek2023-09-151-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In principle, arbitrary notifications may be sent via sd_notify. But in practice, this is not useful at all, since the manager only accepts notifications from services and ignores anything except a few specific ones. The others will be logged if debugging is enabled. OTOH, the manager produces EXIT_STATUS, but nothing in systemd looks at it, which is rather confusing. So remove the recommendation to use X_ prefixes, and instead say that other messages will be ignored. Also, mention that mkosi uses this. Having an example may be useful to understand what is going on. Strangely, this is the first reference to mkosi in our man pages. Even more strangely, debian is the only place which hosts the mkosi man page (among the sites we have definitions for), so I linked to that version.
| * man: make the description of fd storage a bit more accessibleZbigniew Jędrzejewski-Szmek2023-09-152-35/+48
| | | | | | | | | | The text is split into paragraphs about specific topics. The advice and recommendations parts are moved to the end.
| * man/sd_notify: split out variable descriptions to a separate sectionZbigniew Jędrzejewski-Szmek2023-09-151-76/+81
| | | | | | | | | | This just moves the text around with miminal text added to refer to the new section.
| * man/kernel-install: add more paragraph breaks, fix indentationZbigniew Jędrzejewski-Szmek2023-09-151-19/+37
| |
* | man: Mention that JSON user record files should have the .user extensionDaan De Meyer2023-09-181-2/+3
| |
* | doc: add a markdown doc giving an overview over the fdstoreLennart Poettering2023-09-183-7/+16
| | | | | | | | And link it up everywhere.
* | man: fix counting of resource typesLennart Poettering2023-09-181-1/+1
| |
* | man: link UKI spec from sd-stubLennart Poettering2023-09-181-0/+3
| |
* | man: drop duplicate .uname documentation, add .sbat documentationLennart Poettering2023-09-181-9/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the PE section documentation in the systemd-stub man page: for some reason .uname was listed twice, and .sbat was still missing. Address that. Also, let's reorder things to to match the "canonical" ordering we also use for measurement in sd-stub. The order makes sense and there's really no reason to depart from that here. Minor other tweaks. Reverts b6f2e6860220aa89550f690b12246c4e8eb6e908, among other things
* | Merge pull request #29119 from ↵Luca Boccassi2023-09-171-5/+36
|\ \ | | | | | | | | | | | | yuwata/network-dhcp-server-allow-null-server-address network/dhcp-server: allow null server address
| * | man: update [DHCPServer] ServerAddress=Yu Watanabe2023-09-081-5/+36
| | |
* | | doc: Scope is automatic for IPv6 addressTj2023-09-151-0/+1
| | | | | | | | | | | | | | | The kernel automatically sets the scope of IPv6 addresses. That is 0 (global), 254 (host), 253 (link).
* | | man: add versioned version of --no-pager, use for systemd-pathZbigniew Jędrzejewski-Szmek2023-09-142-1/+14
| |/ |/|
* | logind: add PrepareForShutdownWithMetadata signalLuca Boccassi2023-09-111-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | The existing signal doesn't say which type of shutdown is going to happen. With the introduction of soft-reboot, it is useful to have this information broadcasted, so that clients can choose to do different things based on the reboot type. Add a{sv} as the payload so that more metadata can be added later if needed, without needing to add yet another signal. Send both old and new signal for backward compatibility, and send the new one first so that clients can just wait for the first one on both old and new systems.
* | dbus: Document org.freedesktop.systemd1.Service.MemoryAvailable propertyMichal Koutný2023-09-091-4/+5
| | | | | | | | The value is an optimistic estimate, make it clear in the docs.
* | ukify/man: Look for a config file in systemd folders if not specifiedAlvin Alvarado2023-09-081-0/+7
|/ | | | | If the user does not specify a config file to use, ukify will try looking for one at {/run,/etc,/usr/local/lib,/usr/lib}/systemd/ukify.conf in order and then use the first one found. Also made sure the --config input is a pathlib.Path by specifying its type in its CONFIG_ITEMS entry. Big cheers to Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> for helping!
* parse_timestamp: accept RFC3339-style timezone and %FT%R[:%S[.%N]]наб2023-09-071-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We basically parsed the RFC3339 format already, except with a space: NOTE: ISO 8601 defines date and time separated by "T". Applications using this syntax may choose, for the sake of readability, to specify a full-date and full-time separated by (say) a space character. so now we handle both 2012-11-23 11:12:13.456 2012-11-23T11:12:13.456 as equivalent. Parse directly-suffixed Z and +05:30 timezones as well: 2012-11-23T11:12:13.456Z 2012-11-23T11:12:13.456+02:00 as they're both defined by RFC3339. We do /not/ allow z or t; the RFC says NOTE: Per [ABNF] and ISO8601, the "T" and "Z" characters in this syntax may alternatively be lower case "t" or "z" respectively. This date/time format may be used in some environments or contexts that distinguish between the upper- and lower-case letters 'A'-'Z' and 'a'-'z' (e.g. XML). Specifications that use this format in such environments MAY further limit the date/time syntax so that the letters 'T' and 'Z' used in the date/time syntax must always be upper case. Applications that generate this format SHOULD use upper case letters. We /are/ in a case-sensitive environment, neither are in wide-spread use, and "z" poses an issue of whether "todayz" should be the same as "todayZ" ("today UTC") or an error (it should be an error). Fractional seconds are limited to six digits (they're nominally time-secfrac = "." 1*DIGIT ), since we only support 1µs-resolution timestamps, and limit to six digits in our other sub-second formats. Parsing 2012-11-23T11:12 is an extension two ways (no seconds, no timezone), mirroring our "canonical" format. Fixes #5194
* Merge pull request #29098 from keszybz/man-page-postreview-fixupLuca Boccassi2023-09-061-6/+8
|\ | | | | man/systemd-id128: fix example
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 02:56:33 +0100