summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | update TODOLennart Poettering2019-08-201-0/+4
| |
* | Merge pull request #13360 from keszybz/udev-watch-moreLennart Poettering2019-08-202-2/+4
|\ \ | | | | | | udev: set "watch" for more devices
| * | udev: allow persistent storage rules work for ubi devicesZbigniew Jędrzejewski-Szmek2019-08-162-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Back in dbbf424c8b77c1649e822c20c0b1fee1d2cfd93d, we merged a rule to add persistent storage for /dev/ubi*, but this rule could have never worked because of the top-level exclude. Also set "watch" for /dev/ubi*.
| * | udev: assume all devices which have persistent links also need to be watchedZbigniew Jędrzejewski-Szmek2019-08-161-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | We had two similar lists, but one was accepting many more device types. I assume that this is by mistake, simply because the lack of device links is easier to notice than the lack of synthesized event after the device is written to. This uses the same list in both places, effectively adding "watch" attribute to /dev/nbd*, /dev/zd*, etc.
* | | cgroup: Also set io.bfq.weightKai Krakow2019-08-202-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current kernels with BFQ scheduler do not yet set their IO weight through "io.weight" but through "io.bfq.weight" (using a slightly different interface supporting only default weights, not per-device weights). This commit enables "IOWeight=" to just to that. This patch may be dropped at some time later. Github-Link: https://github.com/systemd/systemd/issues/7057 Signed-off-by: Kai Krakow <kai@kaishome.de>
* | | Merge pull request #13356 from keszybz/static-nodes-permsLennart Poettering2019-08-194-16/+43
|\ \ \ | | | | | | | | Fix permissions on static nodes
| * | | tmpfiles: override permissions of static nodes that need thisZbigniew Jędrzejewski-Szmek2019-08-193-14/+41
| | | | | | | | | | | | | | | | Fixes #13350.
| * | | Rename tmpfiles.d/kmod.conf to static-nodes.confZbigniew Jędrzejewski-Szmek2019-08-191-2/+2
| | | | | | | | | | | | | | | | | | | | It is generated using kmod, but apart from that doesn't have much to do with kmod.
* | | | Merge pull request #13353 from keszybz/analyze-cat-config-relabel-extra.dLennart Poettering2019-08-193-14/+23
|\ \ \ \ | | | | | | | | | | systemd-analyze cat-config relabel-extra.d/
| * | | | analyze: make cat-config work with relabel-extra.dZbigniew Jędrzejewski-Szmek2019-08-191-9/+18
| | | | |
| * | | | systemctl: use unicode in one more placeZbigniew Jędrzejewski-Szmek2019-08-191-1/+1
| | | | |
| * | | | man: owned to → owned byZbigniew Jędrzejewski-Szmek2019-08-191-4/+4
| |/ / /
* | | | shared/seccomp: add sync_file_range2Zbigniew Jędrzejewski-Szmek2019-08-191-0/+1
| | | | | | | | | | | | | | | | | | | | Some architectures need the arguments to be reordered because of alignment issues. Otherwise, it's the same as sync_file_range.
* | | | Merge pull request #13235 from yuwata/network-routing-policy-rule-family-13233Zbigniew Jędrzejewski-Szmek2019-08-1917-81/+264
|\ \ \ \ | | | | | | | | | | network: add RoutingPolicyRule.Family= setting
| * | | | test-network: add tests for RoutingPolicyRule.Family=ipv6 and bothYu Watanabe2019-08-162-3/+36
| | | | |
| * | | | network: add RoutingPolicyRule.Family= settingYu Watanabe2019-08-167-2/+101
| | | | | | | | | | | | | | | | | | | | Closes #13233.
| * | | | network: split out copying logic from routing_policy_rule_add_internal()Yu Watanabe2019-08-161-29/+42
| | | | |
| * | | | network: rename AddressFamilyBoolean -> AddressFamilyYu Watanabe2019-08-1610-37/+37
| | | | | | | | | | | | | | | | | | | | We usually do not call an extended boolean as XxxBoolean.
| * | | | network: add missing entry in serialization/deserializationYu Watanabe2019-08-162-7/+17
| | | | |
| * | | | network: serialize/deserialize address familyYu Watanabe2019-08-162-8/+23
| | | | |
| * | | | network: refuse the case To= and From= are in different address familyYu Watanabe2019-08-163-3/+16
| | | | |
* | | | | Merge pull request #13345 from yuwata/network-fix-preferred-lifetime-zero-13341Zbigniew Jędrzejewski-Szmek2019-08-193-8/+14
|\ \ \ \ \ | | | | | | | | | | | | network: fix PreferredLifetime=0
| * | | | | test-network: update test for PreferredLifetime=0Yu Watanabe2019-08-182-4/+13
| | | | | |
| * | | | | network: do not check deprecated flag in address_is_ready()Yu Watanabe2019-08-181-4/+1
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without this change, the address with PreferredLifetime=0 cannot be ready, and thus, no consequent setting up process does not start. The bug was introduced by 6aa5773. Follow-up for b7ed5384ab55cd4d7b8d7d1ec7f5d5e145f0a2b1. Fixes #13341.
* | | | | Revert "shared/conf-parser,networkd: EXTRACT_UNQUOTE|EXTRACT_RETAIN_ESCAPE ↵Zbigniew Jędrzejewski-Szmek2019-08-194-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | → EXTRACT_UNQUOTE" This reverts commit 8a07b4033e5d3c86931b3dd2ddbca41118c05c60. The tests are kept. test-networkd-conf is adjusted to pass. This fixes #13276. I think current rules are extremely confusing, as the case in test-networkd-conf shows. We apply some kinds of unescaping (relating to quoting), but not others (related to escaping of special characters). But fixing this is hard, because people have adjusted quoting to match our rules, and if we make the rules "better", things might break in unexpected places.
* | | | | cgroup-util: update comment to reflect stable kernel fixesTopi Miettinen2019-08-191-1/+2
| |/ / / |/| | |
* | | | Merge pull request #13344 from ddstreet/test-functionsYu Watanabe2019-08-185-52/+44
|\ \ \ \ | | | | | | | | | | Minor/cosmetic changes to test/test-functions, some test.sh
| * | | | test/test-functions: add mkdir to import_initdirDan Streetman2019-08-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This dir is created by create_empty_image_rootdir, as well as indirectly by some other functions, but it should be created by import_initdir so the newly-exported $initdir exists and can be used immediately without relying on other functions to create it.
| * | | | test: replace $TESTDIR/root with $initdirDan Streetman2019-08-173-34/+34
| | | | | | | | | | | | | | | | | | | | | | | | | The $initdir var is already set to $TESTDIR/root, it should be used instead of direct use of $TESTDIR/root.
| * | | | test: TEST-33 and TEST-36 should use create_empty_image_rootdirDan Streetman2019-08-172-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | This recently added function handles mkdir and mounting of the empty image, as well as umounting after test_setup.
| * | | | test/test-functions: avoid stderr noise, only umount on cleanup if mountpointDan Streetman2019-08-171-8/+9
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Only umount it during cleanup if the $TESTDIR/root dir is a mountpoint. This avoids adding noise to the stderr log such as: mountpoint: /var/tmp/systemd-test.waLOFT/root: No such file or directory
* | | | test: increase qemu timeout for TEST-18 and TEST-19Dan Streetman2019-08-182-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These tests runs under qemu, and on some testbeds, without acceleration. On those systems, the current 180 second overall test timeout is too short to run the test. Increasing the timeout to 600s should be enough, even for slow non-accelerated qemu testbeds.
* | | | man: add missing commaTheo Ouzhinski2019-08-171-1/+1
| | | |
* | | | trivial spelling fixes (#13339)Mr-Foo2019-08-171-2/+2
|/ / /
* | | Merge pull request #13317 from ddstreet/werrorZbigniew Jędrzejewski-Szmek2019-08-163-15/+24
|\ \ \ | | | | | | | | Fix build warnings, so Ubuntu CI can pass --werror to meson
| * | | src/boot/efi/meson.build: if meson --werror is true, set gcc -WerrorDan Streetman2019-08-151-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | This part of the build does not use the normal meson parameters, so we need to explicitly check for the meson --werror parameter, and if it's true, set the gcc -Werror parameter for this subdir's build.
| * | | src/boot/efi/linux: elide __attribute__((regparm(0))) on non-i386Dan Streetman2019-08-151-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | This attribute is x86_32-only, so when building on non-intel archs it generates a compiler warning. When building with -Werror this turns into an error, so only include the attribute on i386 arch builds.
| * | | src/boot/efi/shim: elide __attribute__((sysv_abi)) on non-intel archsDan Streetman2019-08-151-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | This attribute is x86-only, so when building on non-intel archs it generates a compiler warning. When building with -Werror this turns into an error, so only include the attribute on intel archs.
* | | | po: update Ukrainian translation (#13329)Yuri Chornoivan2019-08-161-16/+112
| | | | | | | | | | | | | | | | | | | | | | | | * Update Ukrainian translation * po: update Ukrainian translation
* | | | unit-file: downgrade accidentaly high-prio debug log messageLennart Poettering2019-08-161-1/+1
| | | |
* | | | networkctl: avoid outputting '(null)' for LLDP ports without descriptionLennart Poettering2019-08-161-1/+1
|/ / /
* | | src/basic/missing_syscall: add comment lines for PR 13319 changesDan Streetman2019-08-151-0/+9
| | | | | | | | | | | | | | | | | | | | | Add a comment line explaining that the syscall defines might be defined to invalid negative numbers, as libseccomp redefines them to negative numbers if not defined by the kernel headers, which is not obvious just from reading the code checking for defined && > 0
* | | README: add an OSS-Fuzz badgeEvgeny Vereshchagin2019-08-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Since bug reports, backtraces, coverage reports and build logs are scattered across at least four different places and there is no publicly available dashboards the badge can point to, let's just point it to the build logs, which hopefully are going to be a little bit more usable once https://github.com/google/oss-fuzz/issues/2690 is addressed.
* | | update-utmp: fix assertion failure if rescue.target, multi-user.target and ↵Tommi Rantala2019-08-141-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | graphical.target are all inactive If rescue.target, multi-user.target and graphical.target are all inactive, get_current_runlevel() is not able to determine current runlevel, and returns with zero. This zero runlevel value results to assertion failure in utmp_put_runlevel(). # systemctl stop rescue.target multi-user.target graphical.target # systemctl start systemd-update-utmp-runlevel.service systemd[1]: Stopped target Graphical Interface. systemd[1]: Stopped target Multi-User System. systemd[1]: Starting Update UTMP about System Runlevel Changes... systemd-update-utmp[67]: Assertion 'runlevel > 0' failed at src/shared/utmp-wtmp.c:275, function utmp_put_runlevel(). Aborting. systemd[1]: systemd-update-utmp-runlevel.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: systemd-update-utmp-runlevel.service: Failed with result 'core-dump'. systemd[1]: Failed to start Update UTMP about System Runlevel Changes. Let's just print a warning in this case and skip the utmp update, to avoid systemd-update-utmp-runlevel.service failures.
* | | Merge pull request #13273 from RPigott/zshcompZbigniew Jędrzejewski-Szmek2019-08-142-18/+39
|\ \ \ | | | | | | | | Enable resolvectl zsh completions
| * | | shell-completion: add resolvectl commands to zsh completionRonan Pigott2019-08-071-7/+28
| | | |
| * | | shell-completion: enable resolvectl zsh completionRonan Pigott2019-08-072-14/+14
| | | |
* | | | sysusers: properly mark generated accounts as lockedLennart Poettering2019-08-141-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we'd only set the shell to /usr/bin/nologin and lock the password for system users. Let's go one step further and also lock the whole account. This is a paranoid safety precaution, since neither disabling the shell like this nor disabling the password is sufficient to lock an account, since remote shell tools generally allow passing different shells, and logins into ftp or similar protocols don't know the shell concept anyway. Moreover, in times of ssh authentication by password is just one option of authentication among many. Takes inspiration from the recommendations in usermod(8)'s -L switch: "Note: if you wish to lock the account (not only access with a password), you should also set the EXPIRE_DATE to 1."
* | | | Merge pull request #13298 from RPigott/busctlZbigniew Jędrzejewski-Szmek2019-08-141-2/+217
|\ \ \ \ | | | | | | | | | | zsh: add busctl completions
| * | | | shell-completion: complete --match argument for busctlRonan Pigott2019-08-141-1/+25
| | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-19 01:08:40 +0100