summaryrefslogtreecommitdiffstats
path: root/man/systemd.link.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: asorted fixesYu Watanabe6 days1-4/+4
| | | | Closes #35307.
* man: document that separate /usr/local/ must not be used for configZbigniew Jędrzejewski-Szmek2024-06-111-1/+3
| | | | | | | | | | | | | | Since we document /usr/local/lib/systemd/ and other paths for various things, add notes that this is not supported if /usr/local is a separate partition. In systemd.unit, I tried to add the footnote in the table where /usr/local/lib/systemd/ is listed, but that get's rendered as '[sup]a[/sup]' with a mangled footnote at the bottom of the table :( . Also, split paragraphs in one place where the subject changes without any transition. Follow-up for 02f35b1c905ac63ba62f94efebf858412e961fc1. Replaces https://github.com/systemd/systemd/pull/33231.
* man: fix grammar for Name= option in systemd.linkdrewbug2024-05-201-1/+1
|
* udevd: Add ReceivePacketSteeringCPUMask for systemd.linkRenjaya Raga Zenta2024-02-281-0/+15
| | | | | | | | | | | | | | | | Takes a list of CPU indices or ranges separated by either whitespace or commas. Alternatively, takes the special value "all" in which will include all available CPUs in the mask. CPU ranges are specified by the lower and upper CPU indices separated by a dash (e.g. "2-6"). This option may be specified more than once, in which case the specified CPU affinity masks are merged. If an empty string is assigned, the mask is reset, all assignments prior to this will have no effect. Defaults to unset and RPS CPU list is unchanged. To disable RPS when it was previously enabled, use the special value "disable". Currently, this will set CPU mask to all `rx` queue of matched device (if it has multiple queues). The `/sys/class/net/<dev>/queues/rx-<n>/rps_cpus` only accept cpu bitmap mask in hexadecimal. Fix: #30323
* man: fix references to systemd.exec(5)Lennart Poettering2024-01-111-1/+1
| | | | | | For some reason the section for the systemd.exec man page was added incorrectly and then copypasted everywhere else incorrectly too. Let's fix that.
* udev/net: introduce [Link] Property=, ImportProperty=, and UnsetProperty= ↵Yu Watanabe2024-01-091-0/+94
| | | | | | | settings The applied order is equivalent to Environment=, PassEnvironment=, and UnsetEnvironment= for [Service] or so.
* man: fix indentationYu Watanabe2024-01-091-2/+2
|
* man: use same version in public and system ident.David Tardon2023-12-251-1/+1
|
* man: use <simplelist> for 'See also' sectionsDavid Tardon2023-12-231-12/+12
| | | | | This is just a slight markup improvement; there should be no difference in rendering.
* man: more hyperlinks and other fixesZbigniew Jędrzejewski-Szmek2023-11-061-3/+3
| | | | Closes https://github.com/systemd/systemd/issues/29814.
* man: mention that network files should be prefixed with number smaller than 70Yu Watanabe2023-11-031-2/+2
|
* man: update version informationAbderrahim Kitouni2023-09-191-1/+57
| | | | | | | | 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
* man: add version infoAbderrahim Kitouni2023-08-291-5/+145
| | | | | | | | This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
* Merge pull request #27846 from keszybz/link-mode-generationLennart Poettering2023-06-131-44/+3
|\ | | | | Autogenerate list of link modes
| * man: generate link mode list dynamicallyZbigniew Jędrzejewski-Szmek2023-05-301-44/+3
| | | | | | | | | | | | | | | | The entries are sorted by speed. Some fields are left empty when there is no clear value to use. The table is much longer now, but I think it's better to document the allowed values, even if some are not terribly useful. Fixes #26256.
* | creds: Add ImportCredential=Daan De Meyer2023-06-081-1/+1
|/ | | | | | ImportCredential= takes a credential name and searches for a matching credential in all the credential stores we know about it. It supports globs which are expanded so that all matching credentials are loaded.
* tree-wide: code spelling fixesFrantisek Sumsal2023-04-201-1/+1
| | | | As reported by Fossies.
* man: add an example to (re-)apply new settings to a network interfaceYu Watanabe2023-03-041-0/+17
| | | | Closes #26601.
* man: sync the default .link file in exampleYu Watanabe2023-03-041-6/+9
|
* man: fix explanation for Credential= match in .link filesДамјан Георгиевски2023-01-241-1/+1
| | | | | | .link files are handled by systemd-udevd, not by systemd-networkd, so fix the man page to say that the Credential= match uses credentials set on the systemd-udevd.service
* man: fix issues reported by the manpage-l10n projectZbigniew Jędrzejewski-Szmek2023-01-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #25780. > Man page: crypttab.5 > Issue 1: Missing fullstop > Issue 2: I<cipher=>, I<hash=>, I<size=> → B<cipher=>, B<hash=>, B<size=> > > "Force LUKS mode\\&. When this mode is used, the following options are " > "ignored since they are provided by the LUKS header on the device: " > "I<cipher=>, I<hash=>, I<size=>" Seems OK to me. The full stop is there and has been for at least a few years. And we use <option> for the markup, which is appropriate here. > Man page: crypttab.5 > Issue 1: Missing fullstop > Issue 2: I<cipher=>, I<hash=>, I<keyfile-offset=>, I<keyfile-size=>, I<size=> → B<cipher=>, B<hash=>, B<keyfile-offset=>, B<keyfile-size=>, B<size=> > > "Use TrueCrypt encryption mode\\&. When this mode is used, the following " > "options are ignored since they are provided by the TrueCrypt header on the " > "device or do not apply: I<cipher=>, I<hash=>, I<keyfile-offset=>, I<keyfile-" > "size=>, I<size=>" Same. > Man page: journalctl.1 > Issue 1: make be → may be Fixed. > Issue 2: below\\&. → below: Fixed. > Man page: journalctl.1 > Issue: Colon at the end? > > "The following commands are understood\\&. If none is specified the default " > "is to display journal records\\&." > msgstr "" > "Die folgenden Befehle werden verstanden\\&. Falls keiner festgelegt ist, ist " > "die Anzeige von Journal-Datensätzen die Vorgabe\\&." This is a bit awkward, but I'm not sure how to fix it. > Man page: kernel-install.8 > Issue: methods a fallback → methods fallback It was correct, but I added a comma to make the sense clearer. > Man page: loader.conf.5 > Issue 1: secure boot variables → Secure Boot variables > Issue 2: one → one for (multiple times) > > "Supported secure boot variables are one database for authorized images, one " > "key exchange key (KEK) and one platform key (PK)\\&. For more information, " > "refer to the \\m[blue]B<UEFI specification>\\m[]\\&\\s-2\\u[2]\\d\\s+2, " > "under Secure Boot and Driver Signing\\&. Another resource that describe the " > "interplay of the different variables is the \\m[blue]B<EDK2 " > "documentation>\\m[]\\&\\s-2\\u[3]\\d\\s+2\\&." "one of" would sound strange. "One this and one that" is OK. > Man page: loader.conf.5 > Issue: systemd-boot → B<systemd-boot>(7) Fixed. > Man page: logind.conf.5 > Issue: systemd-logind → B<systemd-logind>(8) We use <filename>systemd-logind</> on subsequent references… I think that's good enough. > Man page: nss-myhostname.8 > Issue: B<getent> → B<getent>(1) Fixed. > Man page: nss-resolve.8 > Issue: B<systemd-resolved> → B<systemd-resolved>(8) The first reference does this, subsequent are shorter. > Man page: os-release.5 > Issue: Portable Services → Portable Services Documentation? Updated. > Man page: pam_systemd_home.8 > Issue: auth and account use "reason", while session and password do not? Reworded. > Man page: portablectl.1 > Issue: In systemd-portabled.service(8): Portable Services Documentation Updated. > Man page: repart.d.5 > Issue: The partition → the partition Fixed. > Man page: repart.d.5 > Issue: B<systemd-repart> → B<systemd-repart>(8) The first reference does this. I also change this one, because it's pretty far down in the text. > Man page: systemd.1 > Issue: kernel command line twice? > > "Takes a boolean argument\\&. If false disables importing credentials from " > "the kernel command line, qemu_fw_cfg subsystem or the kernel command line\\&." Apparently this was fixed already. > Man page: systemd-boot.7 > Issue: enrollement → enrollment Fixed. > Man page: systemd-cryptenroll.1 > Issue: multiple cases: any specified → the specified Reworded. > Man page: systemd-cryptenroll.1 > Issue: If this this → If this Fixed tree-wide. > Man page: systemd-cryptsetup-generator.8 > Issue: and the initrd → and in the initrd "Is honoured by the initrd" is OK, because we often speak about the initrd as a single unit. But in the same paragraph we also used "in the initrd", which makes the other use look sloppy. I changed it to "in the initrd" everywhere in that file. > Man page: systemd.directives.7 > Issue: Why are these two quoted (but not others)? > > "B<\\*(Aqh\\*(Aq>" > > B<\\*(Aqs\\*(Aq>" > > "B<\\*(Aqy\\*(Aq>" This is autogenerated from files… We use slightly different markup in different files, and it's just too hard to make it consistent. We gave up on this. > Man page: systemd.exec.5 > Issue 1: B<at>(1p) → B<at>(1) > Issue 2: B<crontab>(1p) → B<crontab>(1) Fixed. > Man page: systemd.exec.5 > Issue: B<select()> → B<select>(2) Fixed. > Man page: systemd.exec.5 > Issue: qemu → B<qemu>(1) The man page doesn't seem to be in any of the canonical places on the web. I added a link to online docs. > Man page: systemd.exec.5 > Issue: variable → variables Seems to be fixed already. > Man page: systemd-integritysetup-generator.8 > Issue: systemd-integritysetup-generator → B<systemd-integritysetup-generator> I changed <filename> to <command>. > Man page: systemd-integritysetup-generator.8 > Issue: superfluous comma at the end Already fixed. > Man page: systemd-measure.1 > Issue: (see B<--pcr-bank=>) below → (see B<--pcr-bank=> below) Reworded. > Man page: systemd-measure.1 > Issue: =PATH> → =>I<PATH> Fixed. > Man page: systemd-measure.1.po > Issue: B<--bank=DIGEST> → B<--bank=>I<DIGEST> Fixed. > Man page: systemd.netdev.5 > Issue: os the → on the Appears to have been fixed already. > Man page: systemd.netdev.5 > Issue: Onboard → On-board (as in previous string) Updated. > Man page: systemd.network.5 > Issue: B<systemd-networkd> -> B<systemd-networkd>(8) First reference does this, subsequent do not. > Man page: systemd.network.5 > Issue: B<netlabelctl> → B<netlabelctl>(8) First reference does this, subsequent do not. > Man page: systemd.network.5 > Issue: Missing verb (aquired? configured?) in the half sentence starting with "or by a " I dropped the comma. > Man page: systemd-nspawn.1 > Issue: All host users outside of that range → All other host users Reworded. > # FIXME no effect → no effect\\&. > #. type: Plain text > #: archlinux debian-unstable fedora-rawhide mageia-cauldron opensuse-tumbleweed > msgid "" > "Whichever ID mapping option is used, the same mapping will be used for users " > "and groups IDs\\&. If B<rootidmap> is used, the group owning the bind " > "mounted directory will have no effect" A period is added. Not sure if there's some other issue. > Man page: systemd-oomd.service.8 > Issue: B<systemd> → B<systemd>(1) Done. > Man page: systemd.path.5 > Issue 1: B<systemd.exec>(1) → B<systemd.exec>(5) > Issue 2: This section does not (yet?) exist Fixed. > Man page: systemd-pcrphase.service.8 > Issue 1: indicate phases into TPM2 PCR 11 ?? > Issue 2: Colon at the end of the paragraph? Fixed. > Man page: systemd-pcrphase.service.8 > Issue: final boot phase → final shutdown phase? Updated. > Man page: systemd-pcrphase.service.8 > Issue: for the the → for the Fixed tree-wide. > Man page: systemd-portabled.service.8 > Issue: In systemd-portabled.service(8): Portable Services Documentation Updated. > Man page: systemd-pstore.service.8 > Issue: Here and the following paragraphs: . → \\&. // Upstream: What does this comment mean? // You normally write \\&. for a full dot (full stop etc.); here you write only "." (i.e. a plain dot). > > "and we look up \"localhost\", nss-dns will send the following queries to " > "systemd-resolved listening on 127.0.0.53:53: first \"localhost.foobar.com\", " > "then \"localhost.barbar.com\", and finally \"localhost\". If (hopefully) the " > "first two queries fail, systemd-resolved will synthesize an answer for the " > "third query." Looks all OK to me. > Man page: systemd.resource-control.5 > Issue: Missing closing bracket after link to Control Groups version 1 Fixed. > Man page: systemd-sysext.8 > Issue: In systemd-portabled.service(8): Portable Services Documentation Updated. > Man page: systemd.timer.5 > Issue 1: B<systemd.exec>(1) → B<systemd.exec>(5) > Issue 2: This section does not (yet?) exist Fixed. > Man page: systemd.unit.5 > Issue: that is → that are Fixed. > Man page: systemd-veritysetup-generator.8 > Issue: systemd-veritysetup-generator → B<systemd-veritysetup-generator> > > "systemd-veritysetup-generator implements B<systemd.generator>(7)\\&." > > "systemd-veritysetup-generator understands the following kernel command line " > "parameters:" Updated. > Man page: systemd-volatile-root.service.8 > Issue: initrdyes → Initrd Fixed. > Man page: sysupdate.d.5 > Issue: : → \\&. (As above in TRANSFER) Updated. > Man page: sysupdate.d.5 > Issue: some → certain Updated. > Man page: sysupdate.d.5 > Issue 1: i\\&.e\\& → I\\&.e\\& Fixed. > Issue 2: the image → the system "image" seems correct. > Man page: tmpfiles.d.5 > Issue: systemd-tmpfiles → B<systemd-tmpfiles>(8) Updated.
* man: document restrictions on naming interfacesLennart Poettering2022-10-191-9/+22
| | | | | | | | Let's document that "." is a bad choice of character when naming interfaces. Let's also document the hard restrictions we make when naming interfaces. Result of the mess that is #25052.
* man: fix copy/paste typoLennart Poettering2022-07-151-6/+6
|
* pid1: add mechanism for conditionalizing units/network/netdev/link based on ↵Lennart Poettering2022-07-151-0/+12
| | | | | | | credentials passed in This is useful when provisioning systems via nspawn/qemu and running specific services only if specific data is passed into the system.
* man: recommend that .network or friends should have a numeric prefixYu Watanabe2022-04-171-14/+21
| | | | Closes #23105.
* man: various issues reported in #22432Zbigniew Jędrzejewski-Szmek2022-02-231-1/+1
| | | | Fixes #22432.
* network,udev/net: add Kind= settings in [Match] sectionYu Watanabe2022-02-171-0/+14
| | | | | | | This may be useful for writing .network or .link files matching with virtual interfaces. Closes #22541.
* udev/net: support to set MDI-X modeYu Watanabe2022-02-081-0/+15
| | | | Closes #22386.
* udev/net: allow to set number of SR-IOV virtual functionsYu Watanabe2022-01-191-0/+9
| | | | This adds SR-IOVVirtualFunctions= setting in [Link] section.
* udev/net: also support [SR-IOV] section in .link filesYu Watanabe2022-01-191-0/+89
| | | | | | | | The same section is already supported by .network files. But such low-level inteerface setting should be done by udevd, instead of networkd. Let's also support the same semantics by .link files. Prompted by https://github.com/systemd/systemd/issues/20474#issuecomment-901901360.
* network,udev: make .network and .link file can match with hardware address ↵Yu Watanabe2021-11-251-8/+45
| | | | longer or shorter than ETH_ALEN
* udev/net: introduce WakeOnLanPassword=Yu Watanabe2021-10-061-2/+24
| | | | Closes #20913.
* link: connect 5 more properties to ethtool featuresAnita Zhang2021-09-241-0/+35
| | | | | | | | | Sets up the follow properties and their corresponding ethtool feature: - ReceiveVLANCTAGHardwareAcceleration == rx-vlan-hw-parse (or rxvlan) - TransmitVLANCTAGHardwareAcceleration == tx-vlan-hw-insert (or txvlan) - ReceiveVLANCTAGFilter == rx-vlan-filter - TransmitVLANSTAGHardwareAcceleration == tx-vlan-stag-hw-insert - NTupleFilter == rx-ntuple-filter (or ntuple)
* link: Add support for rx-gro-hw nic featureDaan De Meyer2021-08-201-0/+7
|
* link: Stop prefixing features with "the"Daan De Meyer2021-08-201-10/+10
|
* udev: Add support for configuring nic coalescing settingsDaan De Meyer2021-08-201-0/+71
| | | | These are configured via the corresponding ethtool ioctl.
* udev: make RxChannels= or friends also accept "max"Yu Watanabe2021-08-181-40/+9
| | | | | | | | | | Follow-up for 406041b7de767316674eb6a2f98ad466577ce8a4. Also, this makes - the settings accept an empty string, - if the specified value is too large, also use the advertised maximum value. - mention the range of the value in the man page.
* udev: Support "max" string for BufferSize options (#20458)Daan De Meyer2021-08-181-8/+12
| | | | | | | | "max" indicates the hardware advertised maximum queue buffer size should be used. The max sizes can be checked by running `ethtool -g <dev>` (Preset maximums). Since the buffer sizes can't be set to 0 by users, internally we use 0 to indicate that the hardware advertised maximum should be used.
* man: fix assorted issues reported by the manpage-l10n projectZbigniew Jędrzejewski-Szmek2021-07-271-5/+5
| | | | Fixes #20297.
* tree-wide: "a" -> "an"Yu Watanabe2021-06-301-1/+1
|
* udev: make WakeOnLan= take multiple featuresYu Watanabe2021-06-081-9/+6
| | | | WAKE_XXX are flag, not enum.
* man: mention that drop-in files are merged in alphanumeric orderYu Watanabe2021-05-201-3/+3
| | | | This addresses the request in https://github.com/systemd/systemd/issues/19467#issuecomment-829332877.
* man: network: use `networkctl list` instead of `status` to list network ↵Lucas Magasweran2021-05-101-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | interface type To determine the network interface type for use in the `Type=` directive, it is more concise to use the `list` command. Whereas, the `status` command requires an interface parameter. For example, on a RaspberryPi 4 the following shows that the `wlan0` interface type `wlan` is more coveniently listed by the `list` command. ``` root@raspberrypi4-64:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether routable configured 3 wlan0 wlan off unmanaged 3 links listed. ``` Whereas the `networkctl status` command doesn't include this information. ``` root@raspberrypi4-64:~# networkctl status ● State: routable Address: 192.168.1.141 on eth0 fd8b:8779:b7a4::f43 on eth0 fd8b:8779:b7a4:0:dea6:32ff:febe:d1ce on eth0 fe80::dea6:32ff:febe:d1ce on eth0 Gateway: 192.168.1.1 (CZ.NIC, z.s.p.o.) on eth0 DNS: 192.168.1.1 May 07 14:17:18 raspberrypi4-64 systemd-networkd[212]: eth0: Gained carrier May 07 14:17:19 raspberrypi4-64 systemd-networkd[212]: eth0: Gained IPv6LL May 07 14:17:19 raspberrypi4-64 systemd-networkd[212]: eth0: DHCPv6 address fd8b:8779:b7a4::f43/128 timeout preferred -1 valid -1 May 07 14:17:21 raspberrypi4-64 systemd-networkd[212]: eth0: DHCPv4 address 192.168.1.141/24 via 192.168.1.1 ``` To get the interface type using the `status` command you need to specify an additional argument. ``` root@raspberrypi4-64:~# networkctl status wlan0 ● 3: wlan0 Link File: /lib/systemd/network/99-default.link Network File: n/a Type: wlan State: off (unmanaged) Path: platform-fe300000.mmcnr Driver: brcmfmac HW Address: dc:a6:32:be:d1:cf (Raspberry Pi Trading Ltd) MTU: 1500 (min: 68, max: 1500) QDisc: noop IPv6 Address Generation Mode: eui64 Queue Length (Tx/Rx): 1/1 ```
* Add support for conditions on the machines firmwareUwe Kleine-König2021-04-281-0/+12
| | | | | | This allows to limit units to machines that run on a certain firmware type. For device tree defined machines checking against the machine's compatible is also possible.
* udev/net: make .link files support drop-in configYu Watanabe2021-03-051-17/+25
|
* network,udev: move TransmitQueues=/ReceiveQueues= from .network to .linkYu Watanabe2021-02-031-0/+14
| | | | | | | | | As the settings are mostly hardware setup, and merely see from network layer. See also discussions in https://github.com/systemd/systemd/pull/18170#issuecomment-758807497 https://github.com/orgs/systemd/teams/systemd/discussions/1
* udev: rename TxQueueLength= -> TransmitQueueLength=Yu Watanabe2021-02-031-1/+1
| | | | | | | | | As we usually (unfortunately not always though) do not use abbreviations. Tx may be standard abbreviation, but we already have e.g. TransmitChecksumOffload=. So, let's use Transmit instead of Tx. Follow-up for ef4a91a7e8d8337a9d65177b09eb7580b25b8f5d.
* man: use ellipses for ranges in range descriptionsZbigniew Jędrzejewski-Szmek2021-01-291-4/+4
| | | | … and in few other places ;)
* udev: introduce TxQueueLength= settingUlrich Ölmann2021-01-131-0/+7
| | | | | | | | | Enable udev to set the transmit queue length of a device via a new directive to be used in link files. The kernel stores this parameter as an unsigned 32 bit integer. As typical values currently range in the order of 10 to a few 10,000 packets reduce the domain of valid values for this directive to 0..4294967294 and take the excluded 4294967295 == UINT32_MAX to indicate that the directive is unset.
* link: Add support to configure Generic Segment OffloadSusant Sahani2021-01-121-0/+16
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 15:41:41 +0100