summaryrefslogtreecommitdiffstats
path: root/man/systemd-journald.service.xml (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-01-10bash-completion: busctrl: support --full command line optionYu Watanabe1-2/+2
2020-01-10busctl: introduce --full command line optionYu Watanabe2-0/+19
2020-01-10bash-completion: networkctl: do not show ellipsized link nameYu Watanabe1-1/+1
2020-01-10networkctl: set table width 0 when --full is specifiedYu Watanabe2-1/+16
2020-01-10systemd-mount: add --full command line optionYu Watanabe2-1/+20
2020-01-10format-table: allow forcing arbitrary width tablesLennart Poettering1-3/+4
Useful for implementing systemctl's --full. See #14470
2020-01-09man: describe "symlink" and "systemctl link" explicitly in UNIT FILE LOAD PATHHATAYAMA Daisuke1-4/+6
There are sometimes users who put unit files in a location that is inaccessible when systemd starts although they are not found and thus not started because the corresponding mount units have not activated yet. There is already a warning for such issue in man 8 systemctl: link PATH... ...<snip>... The file system where the linked unit files are located must be accessible when systemd is started (e.g. anything underneath /home or /var is not allowed, unless those directories are located on the root file system). However, it looks that it's difficult to find the warning because introductory users typically doesn't know systemctl link. Although there is a description in UNIT FILE LOAD PATH pointing to systemctl link, symlink is now not explicitly mentioned there and thus users doesn't easily get aware of they should read it. To deal with this, let's describe "symlink" and "systemctl link" more explicitly in UNIT FILE LOAD PATH.
2020-01-09bash-completion: networkctl: support --full and --linesYu Watanabe1-2/+2
2020-01-09core: be more restrictive on the dependency types we allow to be created ↵Lennart Poettering1-0/+15
transiently We should allow the ones that the [Unit] section of regular unit files may accet, but no other, in particular not the internal deps we synthesize as reverse of explicitly configured ones, such was WantedBy=. Fixes: #14251
2020-01-09timedatectl: use format-table.[ch]Yu Watanabe1-59/+187
2020-01-09systemd-mount: add --no-legend command line optionYu Watanabe2-0/+11
2020-01-09systemd-mount: use format-table.[ch]Yu Watanabe1-88/+16
2020-01-09format-table: introduce TABLE_PATHYu Watanabe2-0/+9
2020-01-09core: propagate service state to socket in more load statesLennart Poettering1-1/+6
It makes sense to filter state changes for some load states that shouldn't happen, but the common cases should be accepted, because they might happen during runtime when "systemctl daemon-reload" is issued and unit files changed state in between. Otherwise we lose events. Fixes: #4708
2020-01-09udev: don't import parent ID_FS_ data on partitionsThomas Schmitt1-2/+16
When probing partitions, we inherit important information from the parent disk device such as ID_MODEL, and usage of such properties is seen to be acceptable and well established. However, we need to exclude filesystem information from the properties that get inherited. Information about the device content should not be passed on in this way. For example, Linux distro install media commonly uses an ISO filesystem plus a partition table. The ISO filesystem is detected on the main disk device, but we should not pass down those details to the partitions, some or all of which may be pointing at storage areas completely distinct from the ISO filesystem. This is particularly problematic when adding new partitions on media set up in this way (since the new partitions are then reported to contain the parent device's ISO filesystem), or when dealing with more unusual hybrid ISO layouts. The inaccuracy of information here inversely affects users of blkid and udev's persistent storage symlinks. Exclude ID_FS_* properties from the inheritance chain to avoid these problems. Fixes: #14408
2020-01-08sd-event: use _cleanup_ in one more placeZbigniew Jędrzejewski-Szmek1-6/+5
2020-01-08sd-event: use RAII for struct epoll_eventZbigniew Jędrzejewski-Szmek1-20/+11
Inspired by #14353.
2020-01-08network: use automatic stack allocation and structured initZbigniew Jędrzejewski-Szmek1-15/+13
2020-01-08network: do not require ethtool_get_permanent_macaddr() to get an fdZbigniew Jędrzejewski-Szmek3-5/+7
2020-01-08test: minor typo fixLennart Poettering1-1/+1
As pointed out on: https://github.com/systemd/systemd/pull/14465#discussion_r364152064
2020-01-08test: pin meson to 0.52.1 for fuzzit/fuzzbuzzFrantisek Sumsal4-3/+15
Latest meson doesn't work with older python 3.5, which is present on Ubuntu 16.04. Let's pin in to the latest working version (0.52.1) until we properly bump all necessary Ubuntu images to 18.04. See: https://github.com/mesonbuild/meson/issues/6427
2020-01-08network: rename *fd to *ethtool_fdZbigniew Jędrzejewski-Szmek2-45/+45
2020-01-08man: use xi:include to avoid duplicationZbigniew Jędrzejewski-Szmek2-149/+58
... and fix some unwarranted discrepancies between the two man pages.
2020-01-08man: fix option nameZbigniew Jędrzejewski-Szmek1-2/+2
2020-01-08doc: tweak grammar in CONTAINER_INTERFACE descriptionZbigniew Jędrzejewski-Szmek1-105/+101
The only non-stylistic change is to replace descriptions of how we are encouraging people to use PrivateTmp= and such, because now they are widely used.
2020-01-08networkctl: show permanent mac address if it is not used nowYu Watanabe1-0/+28
2020-01-08network, udev: introduce PermanentMACAddress= setting in [Match] sectionYu Watanabe15-15/+77
Closes #13983.
2020-01-08Support Plugable UD-PRO8 dockezst0361-1/+4
Add support for Plugable Pro8 docking station for auto-configuring seat
2020-01-08ethtool: introduce ethtool_get_permanent_macaddr()Yu Watanabe2-0/+43
Will be used in later commits.
2020-01-08gpt-auto: don't assume XBOOTLDR is vfatLennart Poettering1-2/+15
Let's not assume "umask=" is a valid mount option for XBOOTLDR partitions unconditionally. Fixes: #14165
2020-01-08network, meson: allow statically linked buildRobert Scheck3-10/+22
Build option "link-networkd-shared" to build a statically linked systemd-networkd by using -Dlink-udev-shared=false -Dlink-networkd-shared=false on systems with full systemd stack except systemd-networkd, such as RHEL/CentOS 8.
2020-01-08zsh: Complete systemctl subcommands in separate tagsDaniel Shahaf1-11/+17
Fixes #14422
2020-01-08shared/sleep-config: do not ignore resume_offset when resume not setZbigniew Jędrzejewski-Szmek1-4/+2
This is most likely a user error, let's make it easier to diagnose.
2020-01-08shared/sleep-config: make swap detection stricter againZbigniew Jędrzejewski-Szmek1-44/+56
To make this easier to understand, let's always log (at debug level) when we accept or reject each device: /swapfile: detection of swap file offset on Btrfs is not supported /swapfile: is a candidate device. /dev/zram0: ignoring zram swap /dev/vdb: ignoring device with lower priority /dev/vdc: ignoring device with lower usable space ... If we know that hibernation will fail, refuse. This includes cases where /sys/power/resume is set and doesn't match any device, or /sys/power/resume_offset is set and we're not on btrfs and it doesn't match. If /sys/power/resume is not set at all, we still accept the device with the highest priority (see 6d176522f5480ea9e9a83de5ef5ea5e0d95b79cb and 88bc86fcf895da0d51ddaf93d17b4280f4e60d74) Tested cases: 1. no swap active → refuse 2. just zram swap active → refuse 3. swapfile on btrfs with /sys/power/resume{,_offset} set → OK 4. swapfile on btrfs with /sys/power/resume set, offset not set → refuse 5. swapfile on btrfs with /sys/power/resume set to nonexistent device, offset set → refuse 6. /sys/power/resume not set, offset set, candidate exists → OK (*) 7. /sys/power/resume not set, offset not set, candidate exists → OK (*) I think this should fail, but I'm leaving that for the next commit.
2020-01-07boot: fix osrel parserLennart Poettering1-1/+1
let's check VERSION instead of VERSION_ID where appropriate. Fixes: #14493
2020-01-07man: stop recommending modprobe -abq in ExecStartPre=Lennart Poettering1-3/+8
2020-01-07units: tweaks to modprobe@.serviceLennart Poettering1-1/+4
Let's use uppercase wording in the description string, like we usually do. Let's allow using this service in early boot. If it's pulled into the initial transaction it's better to finish loading this before sysinit.target. Don't bother with this in containers that lack CAP_SYS_MODULE
2020-01-07unit: make sure to pull in modprobe@loop.service when RootImage= is used ↵Lennart Poettering1-0/+5
with DeviceAllow= Fixes: #14214
2020-01-07bpf-devices: line-break some overly long function signaturesLennart Poettering1-8/+48
2020-01-07units: Split modprobing out into a separate service unitIain Lane4-5/+21
Devices referred to by `DeviceAllow=` sandboxing are resolved into their corresponding major numbers when the unit is loaded by looking at `/proc/devices`. If a reference is made to a device which is not yet available, the `DeviceAllow` is ignored and the unit's processes cannot access that device. In both logind and nspawn, we have `DeviceAllow=` lines, and `modprobe` in `ExecStartPre=` to load some kernel modules. Those kernel modules cause device nodes to become available when they are loaded: the device nodes may not exist when the unit itself is loaded. This means that the unit's processes will not be able to access the device since the `DeviceAllow=` will have been resolved earlier and denied it. One way to fix this would be to re-evaluate the available devices and re-apply the policy to the cgroup, but this cannot work atomically on cgroupsv1. So we fall back to a second approach: instead of running `modprobe` via `ExecStartPre`, we move this out to a separate unit and order it before the units which want the module. Closes #14322. Fixes: #13943.
2020-01-07udev: use dot_or_dot_dot() where appropriateLennart Poettering1-1/+2
2020-01-07man: fix documentation of IBM VIO device namingLennart Poettering1-6/+11
We generate "v" in two different ways, and they got mixed up.
2020-01-07man: slightly extend documentation on difference between ID_NET_NAME_ONBOARD ↵Lennart Poettering1-4/+5
and ID_NET_LABEL_ONBOARD
2020-01-07shared/sleep: use stat() instead of open()+fstat() in one placeZbigniew Jędrzejewski-Szmek1-17/+6
No functional change.
2020-01-07udev: do not use exact match of file permissionYu Watanabe1-1/+1
This partially reverts 25de7aa7b90c23d33ea50ada1e50c5834a414237. Fixes #14473.
2020-01-07nspawn: set original ifname as alternative if it is truncatedYu Watanabe3-10/+99
2020-01-07network: append INTERFACE= attributes for logs corresponds to a netifYu Watanabe12-65/+67
2020-01-07test-network: suppress logs in status commandYu Watanabe2-32/+32
2020-01-07networkctl: status command also shows logs of networkdYu Watanabe2-3/+111
Closes #14050.
2020-01-07man: drop unnecessary white spaceYu Watanabe1-1/+1
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-07 18:32:40 +0100