summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* network: tc: add more options for TBFYu Watanabe2019-12-101-0/+36
|
* Merge pull request #14273 from ssahani/ifbYu Watanabe2019-12-081-0/+3
|\ | | | | network: introduce IFB
| * network: introduce ifb (Intermediate Functional Block)Susant Sahani2019-12-071-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Intermediate Functional Block The Intermediate Functional Block (ifb) pseudo network interface acts as a QoS concentrator for multiple different sources of traffic. Packets from or to other interfaces have to be redirected to it using the mirred action in order to be handled, regularly routed traffic will be dropped. This way, a single stack of qdiscs, classes and filters can be shared between multiple interfaces. Here's a simple example to feed incoming traffic from multiple interfaces through a Stochastic Fairness Queue (sfq): (1) # modprobe ifb (2) # ip link set ifb0 up (3) # tc qdisc add dev ifb0 root sfq
* | network: introduce DAD for static addressSusant Sahani2019-12-061-3/+7
| | | | | | | | Closes #2527.
* | Merge pull request #14235 from fbuihuu/cryptsetup-fixesZbigniew Jędrzejewski-Szmek2019-12-062-9/+35
|\ \ | |/ |/| Cryptsetup fixes
| * cryptsetup: umount encrypted devices before detaching it during shutdownFranck Bui2019-12-051-9/+16
| | | | | | | | | | | | | | This is done by ordering local-fs-pre.target and remote-fs-pre.target after cryptsetup.target and remote-cryptsetup.target respectively. Fixes: #8472
| * crypsetup: introduce x-initrd.attach optionFranck Bui2019-12-051-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This option is an indication for PID1 that the entry in crypttab is handled by initrd only and therefore it shouldn't interfer during the usual start-up and shutdown process. It should be primarily used with the encrypted device containing the root FS as we want to keep it (and thus its encrypted device) until the very end of the shutdown process, i.e. when initrd takes over. This option is the counterpart of "x-initrd.mount" used in fstab. Note that the slice containing the cryptsetup services also needs to drop the usual shutdown dependencies as it's required by the cryptsetup services. Fixes: #14224
* | Merge pull request #14173 from ssahani/tc-sfqAnita Zhang2019-12-041-0/+34
|\ \ | | | | | | network: tc: introduce sfq and tbf
| * | network: tc introduce sfq - Stochastic Fairness QueueingSusant Sahani2019-12-041-0/+7
| | | | | | | | | | | | | | | | | | | | | Stochastic Fairness Queueing is a classless queueing discipline. SFQ does not shape traffic but only schedules the transmission of packets, based on 'flows'. The goal is to ensure fairness so that each flow is able to send data in turn, thus preventing any single flow from drowning out the rest.
| * | networkd tc: introduce tbfSusant Sahani2019-12-041-0/+27
| | | | | | | | | | | | See https://linux.die.net/man/8/tc-tbf
* | | Implement SNI when using DNS-over-TLSGuilhem Lettron2019-12-041-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Some DNS providers need SNI to identify client. This can be used by adding #name to a DNS. Example: [Resolve] DNS=192.168.1.1#example.com
* | | Merge pull request #13886 from poettering/sd-event-pidfdLennart Poettering2019-12-043-34/+155
|\ \ \ | |/ / |/| | add pidfd support to sd-event (but not yet PID 1)
| * | man: document the new sd-event pidfd magicLennart Poettering2019-12-042-24/+136
| | |
| * | man: mention that SIGCHLD has to be blocked before using sd_event_add_child()Lennart Poettering2019-12-041-3/+11
| | |
| * | man: don't claim we'd unblock the specified signal in sd_event_add_signal()Lennart Poettering2019-12-041-8/+9
| | | | | | | | | | | | | | | | | | | | | We don't, the signal remains blocked. We use signalfd() to be able to read the signal events without unblocking the signal. While we are at it, mention that pthread_sigmask() is fine too.
* | | man: document journal rate limit burst multiplierCharles (Chas) Williams2019-12-041-0/+45
|/ / | | | | | | | | | | The actual burst limit is modified by the remaining disk space. This isn't mentioned anywhere in the available documentation and might be a source of surprise for an end user expecting certain behaviors.
* | Merge pull request #14177 from keszybz/use-initrd.targetLennart Poettering2019-12-041-7/+19
|\ \ | | | | | | Use initrd.target in the initramfs
| * | man: document initrd.targetZbigniew Jędrzejewski-Szmek2019-11-281-7/+19
| | |
* | | pid1: add new kernel cmdline arg systemd.cpu_affinity=Lennart Poettering2019-12-041-0/+11
| |/ |/| | | | | | | | | | | | | | | Let's allow configuration of the CPU affinity via the kernel cmdline, overriding CPUAffinity= in /etc/systemd/system.conf Prompted by: https://lists.freedesktop.org/archives/systemd-devel/2019-November/043754.html
* | nspawn: allow Capability=all in systemd.nspawn [EXEC] sectionafg2019-11-291-1/+2
| | | | | | | | | | Just like --capability=all is allowed in the systemd-nspawn command line.
* | man: use literal tag at one more placeYu Watanabe2019-11-281-2/+2
| |
* | man: document sd_event_source_set_floating()Lennart Poettering2019-11-298-0/+125
| | | | | | | | | | | | Let's make sure we get back to 100% man page documentation coverage of our sd-event APIs. We are bad enough at the others, let's get these ones right at least.
* | man: use mkswap@ instead of makeswap@Jan Tojnar2019-11-282-4/+4
| | | | | | | | That is what is linked from systemd.swap(5) and also what the systemd.generator produces.
* | man: don't claim journalctl would still use signalsLennart Poettering2019-11-281-19/+13
| | | | | | | | It's using the varlink interface these days.
* | man: add reference to journald man page from systemd.journal-fields(7)Lennart Poettering2019-11-281-8/+8
| | | | | | | | We had none so far. Which is weird.
* | man: apparently we lowercased STDOUT/STDERR everywhere else in docs, do so ↵Lennart Poettering2019-11-281-2/+2
| | | | | | | | here too
* | man: drop reference to machined, add one for journald insteadLennart Poettering2019-11-281-2/+2
|/ | | | | | We dropped documentation from sd_journal_open_container() long ago (since the call is obsolete), hence drop the reference to machined. But add one in for journald instead.
* man/systemd.link: Add missing verb *be*Paul Menzel2019-11-271-1/+1
|
* network: also assume Table=local for ipv6 route if Type=local, broadcast, ↵Yu Watanabe2019-11-261-6/+13
| | | | | | | anycast or nat (#14148) Also, if Type=multicast and scope is not set, then assume Scope=link. Fixes #14122.
* Merge pull request #14134 from keszybz/variables-and-docsYu Watanabe2019-11-265-50/+42
|\ | | | | Documentation and option parsing fixes
| * man: refer to systemd.syntax(7) from systemd.nspawn(5)Zbigniew Jędrzejewski-Szmek2019-11-252-48/+24
| | | | | | | | | | | | | | | | systemd.nspawn(5) contained a partial repeat of the stuff that is now in the dedicated man page. Let's just refer to that. While at it, do s/searched/searched for/ where appropriate and reword some sentences for brevity.
| * man: document all pager variables for systemctl and systemdZbigniew Jędrzejewski-Szmek2019-11-242-2/+7
| | | | | | | | | | | | In those two pages, we need to include individual entries with xi:include to merge the list less-variables.xml with the other entries, which is obviously error prone. All variables are supported in both tools so add them.
| * basic/terminal-util: add support for $NO_COLORZbigniew Jędrzejewski-Szmek2019-11-241-0/+11
| | | | | | | | See inline comments. Fixes #13752.
* | man: restores ConditionVirtualization documentation (#14138)Steve Ramage2019-11-251-1/+1
|/ | | Resolves #14137. Error introduced in 337b733449924860eb71190e6eff95729909ede6.
* Merge pull request #14099 from keszybz/machine-ref-unref-fixZbigniew Jędrzejewski-Szmek2019-11-221-12/+25
|\ | | | | Fix for the issue when machine cannot be started second time, and better nspawn logging
| * man: use <constant> for capability names in nspawn pageZbigniew Jędrzejewski-Szmek2019-11-221-11/+18
| |
| * nspawn: dump capability list with --capabilities=helpZbigniew Jędrzejewski-Szmek2019-11-221-2/+8
| |
* | Merge pull request #14105 from keszybz/man-directives-cleanupZbigniew Jędrzejewski-Szmek2019-11-2226-103/+113
|\ \ | | | | | | Man formatting and sorting fixes
| * | man: fix a few bogus entries in directives indexZbigniew Jędrzejewski-Szmek2019-11-2112-22/+26
| | | | | | | | | | | | | | | | | | When wrong element types are used, directives are sometimes placed in the wrong section. Also, strip part of text starting with "'", which is used in a few places and which is displayed improperly in the index.
| * | man: change noindex="true" to index="false"Zbigniew Jędrzejewski-Szmek2019-11-2116-42/+42
| | | | | | | | | | | | We nowadays prefer positive options over negative.
| * | man: use <command> not <option> for commands in resolvectl(1)Zbigniew Jędrzejewski-Szmek2019-11-211-39/+45
| |/
* | bootctl: make 'random-seed' handle inability to write system token EFI ↵Lennart Poettering2019-11-211-0/+6
|/ | | | | | | | | | | | | | | | | variable gracefully Apparently some firmwares don't allow us to write this token, and refuse it with EINVAL. We should normally consider that a fatal error, but not really in the case of "bootctl random-seed" when called from the systemd-boot-system-token.service since it's called as "best effort" service after boot on various systems, and hence we shouldn't fail loudly. Similar, when we cannot find the ESP don't fail either, since there are systems (arch install ISOs) that carry a boot loader capable of the random seed logic but don't mount it after boot. Fixes: #13603
* Merge pull request #14036 from keszybz/systectl-add-logs-and-watchdogsZbigniew Jędrzejewski-Szmek2019-11-202-51/+35
|\ | | | | Systemctl add log-level, log-target, service-watchdogs commands
| * analyze: deprecate the commands moved to systemctlZbigniew Jędrzejewski-Szmek2019-11-181-50/+0
| | | | | | | | | | This just removes the commands from --help and the man pages, everything works as before.
| * systemctl: add service-watchdogs commandZbigniew Jędrzejewski-Szmek2019-11-181-0/+11
| | | | | | | | | | The rationale is the same as for log-level/log-target: this controls the behaviour of the manager, and belongs in systemctl.
| * systemctl: add log-level and log-target commandsZbigniew Jędrzejewski-Szmek2019-11-181-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This copies the commands log-level and log-target (to query and set the current settings) from systemd-analyze to systemctl, essentially reverting a65615ca5d78be0dcd7d9c9b4a663fa75f758606. Controllling the log level settings of the manager is basic functionality, that should be available even if systemd-analyze (which is more of an analysis tool) is not installed. This is like dmesg and journalctl, which should be available even if a debugger and more advanced tools to analyze the kernel are not available. (Note that dmesg is used to control the log level too, not just to browse the kernel logs.) I chose to copy&paste the methods from analyze.c to the new location. There isn't enough code to share, because acquire_bus() in both places has a different signature despite the same name, so the only part that is common is the invocation of sd_bus_set_property().
* | Merge pull request #14074 from keszybz/rename-system-optionsZbigniew Jędrzejewski-Szmek2019-11-201-1/+1
|\ \ | | | | | | Rename system-options
| * | Rename "system-options" to "systemd-efi-options"Zbigniew Jędrzejewski-Szmek2019-11-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes the naming more consistent: we now have bootctl systemd-efi-options, $SYSTEMD_EFI_OPTIONS and the SystemdOptions EFI variable. (SystemdEFIOptions would be redundant, because it is only used in the context of efivars, and users don't interact with that name directly.) bootctl is adjusted to use 2sp indentation, similarly to systemctl and other programs. Remove the prefix with the old name from 'bootctl systemd-efi-options' output, since it's redundant and we don't want the old name anyway.
* | | Merge pull request #14064 from ↵Zbigniew Jędrzejewski-Szmek2019-11-181-17/+17
|\ \ \ | |/ / |/| | | | | | | | yuwata/network-unify-send-option-and-send-raw-option network: unify SendOption= and SendRawOption=
| * | network: rename SendRawOption= to SendOption=Yu Watanabe2019-11-181-17/+17
| |/ | | | | | | | | As DHCPv4.SendOption= and DHCPServer.SendRawOption= take the same format.
View Lorry Controller Status