summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* man: document new featuresLennart Poettering2020-12-1710-94/+603
|
* Merge pull request #17702 from rnhmjoj/masterLennart Poettering2020-12-161-4/+5
|\ | | | | Extend $SYSTEMD_COLORS to switch colors mode
| * basic/term-util: extend $SYSTEMD_COLORSrnhmjoj2020-12-151-4/+5
| | | | | | | | | | | | | | This commit extends $SYSTEMD_COLORS to an enum variable (compared to a simple boolean) which specifies the "colors mode". This means that, in addition to disabling colors altogether, it's now possible to restrict the console output to 16 or 256 colors only.
* | tree-wide: fix typoYu Watanabe2020-12-161-1/+1
| |
* | tree-wide: fix typoYu Watanabe2020-12-162-2/+2
| |
* | hostnamed,shared/hostname-setup: expose the origin of the current hostnameZbigniew Jędrzejewski-Szmek2020-12-161-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In hostnamed this is exposed as a dbus property, and in the logs in both places. This is of interest to network management software and such: if the fallback hostname is used, it's not as useful as the real configured thing. Right now various programs try to guess the source of hostname by looking at the string. E.g. "localhost" is assumed to be not the real hostname, but "fedora" is. Any such attempts are bound to fail, because we cannot distinguish "fedora" (a fallback value set by a distro), from "fedora" (received from reverse dns), from "fedora" read from /etc/hostname. /run/systemd/fallback-hostname is written with the fallback hostname when either pid1 or hostnamed sets the kernel hostname to the fallback value. Why remember the fallback value and not the transient hostname in /run/hostname instead? We have three hostname types: "static", "transient", fallback". – Distinguishing "static" is easy: the hostname that is set matches what is in /etc/hostname. – Distingiushing "transient" and "fallback" is not easy. And the "transient" hostname may be set outside of pid1+hostnamed. In particular, it may be set by container manager, some non-systemd tool in the initramfs, or even by a direct call. All those mechanisms count as "transient". Trying to get those cases to write /run/hostname is futile. It is much easier to isolate the "fallback" case which is mostly under our control. And since the file is only used as a flag to mark the hostname as fallback, it can be hidden inside of our /run/systemd directory. For https://bugzilla.redhat.com/show_bug.cgi?id=1892235.
* | hostnamed: stop discriminating against "localhost" in /etc/hostnameZbigniew Jędrzejewski-Szmek2020-12-161-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We would sometimes ignore localhost-style names in /etc/hostname. That is brittle. If the user configured some hostname, it's most likely because they want to use that as the hostname. If they don't want to use such a hostname, they should just not create the config. Everything becomes simples if we just use the configured hostname as-is. This behaviour seems to have been a workaround for Anaconda installer and other tools writing out /etc/hostname with the default of "localhost.localdomain". Anaconda PR to stop doing that: https://github.com/rhinstaller/anaconda/pull/3040. That might have been useful as a work-around for other programs misbehaving if /etc/hostname was not present, but nowadays it's not useful because systemd mostly controls the hostname and it is perfectly happy without that file. Apart from making things simpler, this allows users to set a hostname like "localhost" and have it honoured, if such a whim strikes them.
* | hostnamed: expose the fallback-hostname setting as a const dbus propertyZbigniew Jędrzejewski-Szmek2020-12-161-0/+7
| | | | | | | | | | | | Various users want to know what the fallback hostname is. Since it was made configurable in 8146c32b9264a6915d467a5cab1a24311fbede7e, we didn't expose this nicely.
* | man/hostnamectl,hostaned,hostname1: adjust the docs to match realityZbigniew Jędrzejewski-Szmek2020-12-164-89/+126
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The semantics were significantly changed in c779a44222161155c039a7fd2fd304c006590ac7 ("hostnamed: Fix the way that static and transient host names interact", Feb. 2014), but when the dbus api documentation was imported much later, it wasn't properly adjusted to describe those new semantics. 34293dfafd2a81d80727938199769906dab321bd which added systemd.hostname= also added new behaviour. Let's ove various bits and pieces around so that they are in more appropriate places. Drop recommendations to set the hostname for DHCP or mDNS purposes. Nowadays we expect tools that want to expose some different hostname to the outside to manage that internally without affecting visible state. Also drop mentions of DHCP or mDNS directly setting the hostname, since nowadays network management software is expected to (and does) go through hostnamed. Also, add a high-level description of semantics. It glosses over the details of handling of localhost-style names. Later commits will remove this special handling anyway.
* | coredumpctl: Add --debugger-args= optionMichal Fabik2020-12-161-1/+17
| | | | | | | | | | | | | | This commit adds the possibility to pass command line options to the debugger invoked with coredumpctl debug. Resolves: #9905
* | network: Allow to configure interface promiscuous modeSusant Sahani2020-12-151-3/+10
| |
* | man: document new ability to connect to user of containerLennart Poettering2020-12-152-4/+28
| |
* | timesync: Make delaying attempts to contact servers configurableSusant Sahani2020-12-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``` ❯ ssh sus@xx.xx.xx.xx Last login: Sat Nov 14 17:32:08 2020 from 10.104.45.138 17:36:19 up 0 min, 0 users, load average: 0.00, 0.00, 0.00 > systemd-analyze blame Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs > systemd-analyze blame 43.954s systemd-time-wait-sync.service 1.969s systemd-networkd-wait-online.service 1.559s cloud-init-local.service 1.039s cloud-init.service 414ms cloud-final.service 387ms dracut-initqueue.service 382ms initrd-switch-root.service 380ms cloud-config.service 198ms systemd-journal-flush.service 136ms systemd-udev-trigger.service 115ms initrd-parse-etc.service 97ms systemd-timesyncd.service 84ms systemd-journald.service ``` After made it configurable and set to 5s ``` ❯ ssh sus@xx.xx.xx.xx Last login: Sat Nov 14 18:41:42 2020 from 10.104.45.138 18:42:36 up 0 min, 0 users, load average: 0.16, 0.03, 0.01 > systemd-analyze blame 10.450s systemd-time-wait-sync.service 8.303s systemd-networkd-wait-online.service 1.621s cloud-init-local.service 1.068s cloud-init.service ```
* | tree-wide: fix typoYu Watanabe2020-12-141-1/+1
|/
* man: mention new OPTIONS=log_level= udev ruleYu Watanabe2020-12-101-0/+18
|
* man: document that automount units are privilegedLennart Poettering2020-12-092-0/+7
| | | | Fixes: #17886
* man: synthetize(d) -> synthesize(d)Yu Watanabe2020-12-081-4/+4
|
* systemd-nspawn: Allow setting ambient capability setTorsten Hilbrich2020-12-072-3/+59
| | | | | | | | | | | | | | | | | | | | | | | | The old code was only able to pass the value 0 for the inheritable and ambient capability set when a non-root user was specified. However, sometimes it is useful to run a program in its own container with a user specification and some capabilities set. This is needed when the capabilities cannot be provided by file capabilities (because the file system is mounted with MS_NOSUID for additional security). This commit introduces the option --ambient-capability and the config file option AmbientCapability=. Both are used in a similar way to the existing Capability= setting. It changes the inheritable and ambient set (which is 0 by default). The code also checks that the settings for the bounding set (as defined by Capability= and DropCapability=) and the setting for the ambient set (as defined by AmbientCapability=) are compatible. Otherwise, the operation would fail in any way. Due to the current use of -1 to indicate no support for ambient capability set the special value "all" cannot be supported. Also, the setting of ambient capability is restricted to running a single program in the container payload.
* core: add ConditionSecurity=tpm2 supportLennart Poettering2020-12-031-3/+3
|
* Adds missing documentation for Assertions (#17825)Steve Ramage2020-12-031-0/+4
|
* network: add Protocol= to vlan netdev (#17794)walbit-de2020-12-021-0/+7
|
* tree-wide: fix typosYu Watanabe2020-12-021-1/+1
|
* Merge pull request #17692 from yuwata/ipv4llZbigniew Jędrzejewski-Szmek2020-12-011-14/+13
|\ | | | | network: fold ipv4ll fallback modes into normal ipv4ll addressing
| * networkd: start ipv4ll when dhcp has trouble getting a leaseZbigniew Jędrzejewski-Szmek2020-11-301-2/+5
| | | | | | | | Fixes #13316.
| * networkd: merge ll addressing fallback modes into normal "boolean" valuesZbigniew Jędrzejewski-Szmek2020-11-301-11/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | They are not really boolean, because we have both ipv4 and ipv6, but for each protocol we have either unset, no, and yes. From https://github.com/systemd/systemd/issues/13316#issuecomment-582906817: LinkLocalAddressing must be a boolean option, at least for ipv4: - LinkLocalAddressing=no => no LL at all. - LinkLocalAddressing=yes + Static Address => invalid configuration, warn and interpret as LinkLocalAddressing=no, no LL at all. (we check that during parsing and reject) - LinkLocalAddressing=yes + DHCP => LL process should be subordinated to the DHCP one, an LL address must be acquired at start or after a short N unsuccessful DHCP attemps, and must not stop DHCP to keeping trying. When a DHCP address is acquired, drop the LL address. If the DHCP address is lost, re-adquire a new LL address. (next patch will move in this direction) - LinkLocalAddressing=fallback has no reason to exist, because LL address must always be allocated as a fallback option when using DHCP. Having both DHCP and LL address at the same time is an RFC violation, so LinkLocalAdressing=yes correctly implemented is already the "fallback" behavior. The fallback option must be deprecated and if present in older configs must be interpreted as LinkLocalAddressing=yes. (removed) - And for IPv6, the LinkLocalAddress option has any sense at all? IPv6-LL address aren't required to be always set for every IPv6 enabled interface (in this case, coexisting with static or dynamic address if any)? Shouldn't be always =yes? (good question) This effectively reverts 29e81083bd2fcb2dbf83f67ef358c7d25adf7e9d. There is no special "fallback" mode now, so the check doesn't make sense anymore.
| * man: adjust description of MaxAttemptsZbigniew Jędrzejewski-Szmek2020-11-301-3/+3
| | | | | | | | | | The code was changed in 715cedfbf03a2eb1d4dca5d1b2b876e52a3b652d to allow more than six attempts and the old description stopped making sense.
* | Merge pull request #17703 from poettering/event-ratelimitZbigniew Jędrzejewski-Szmek2020-12-014-1/+156
|\ \ | | | | | | sd-event: add a concept of ratelimiting
| * | man: document new ratelimiting APIsLennart Poettering2020-12-014-1/+156
| | |
* | | man: drop comment about ECC vs. RSA and YubikeyLennart Poettering2020-12-011-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The comment is pointless, ECC systematically doesn't allow encryption/decryption directly, only RSA does that. If you want to use ECC for asymmetric encryption/decryption you have to combine it with key exchange scheme and symmetric scheme. This all is not a limitation of the Yubikey, hence don't claim so. It's just how ECC is.
* | | man: document how cryptsetup keys may be acquired via AF_UNIX socketsLennart Poettering2020-12-011-19/+58
| | |
* | | man: mention that --key= is about *secret* keysLennart Poettering2020-12-012-3/+3
|/ /
* | man: Speicfy exact return values of sd_bus_message_enter_containerigo958622020-11-301-2/+7
|/
* resolved: allow cache responses from local DNS serversPavel Sapezhko2020-11-271-2/+10
|
* man: slightly update the man page of sd_bus_message_read_basic()Yu Watanabe2020-11-251-1/+1
| | | | Follow-up for 73a1d7d2433edd1872ec53db3e804009298ebb1d.
* man: Fixed an incomplete sentenceigo958622020-11-251-1/+1
|
* man: Specify that sd_bus_message_read_basic returns 0 if end of array had ↵igo958622020-11-251-3/+3
| | | | been reached.
* Merge pull request #17715 from yuwata/specifier-follow-upsZbigniew Jędrzejewski-Szmek2020-11-252-30/+29
|\ | | | | Sort specifiers
| * man: sort specifiers alphabeticallyYu Watanabe2020-11-252-26/+26
| |
| * man: add missing specifiers supported in [INSTALL] sectionYu Watanabe2020-11-251-4/+3
| |
* | man: clarify DefaultTasksMax docPavel Sapezhko2020-11-251-2/+4
| |
* | tree-wide: fix typoYu Watanabe2020-11-251-1/+1
|/
* Merge pull request #17680 from yuwata/udev-link-mac-addressLennart Poettering2020-11-241-4/+7
|\ | | | | udev: to make MACAddress= take effect, MACAddressPolicy= must be "none"
| * man: to make MACAddress= take effect, MACAddressPolicy= must be "none"Yu Watanabe2020-11-201-4/+7
| |
* | man: bootctl set-default/oneshot accept an empty stringYu Watanabe2020-11-241-0/+1
| |
* | gpt: add RISC-V GPT partition typecode uuidDimitri John Ledkov2020-11-232-0/+54
| |
* | man: Fix misspelling of directive and typos in systemd-coredump man pagevanou2020-11-231-4/+4
|/ | | | | | | This commit fixes * misspelling of LimitCORE directive of systemd.exec * typos in systemd-coredump man page.
* man: suffix settings name with = and enclose in <varname>Lennart Poettering2020-11-191-6/+4
|
* man: Fix sd_bus_message_append_array_space function signatureigo958622020-11-181-0/+1
|
* man,NEWS: fix "the the"Yu Watanabe2020-11-181-2/+2
|
* Merge pull request #17643 from keszybz/man-news-independentZbigniew Jędrzejewski-Szmek2020-11-171-14/+15
|\ | | | | NEWS and man page tweaks
View Lorry Controller Status