summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* NEWS: two minor entriesv245-rc2Zbigniew Jędrzejewski-Szmek2020-03-031-0/+9
|
* NEWS: update contributors listZbigniew Jędrzejewski-Szmek2020-03-032-20/+27
|
* hwdb: update for v245-rc2Zbigniew Jędrzejewski-Szmek2020-03-0311-1180/+3199
|
* network: Move config_parse_ip_service_type to networkd-dhcp4.c andSusant Sahani2020-03-035-29/+30
| | | | rename
* Merge pull request #14992 from keszybz/syslog-address-length-fixZbigniew Jędrzejewski-Szmek2020-03-0218-101/+120
|\ | | | | Syslog address length fix
| * ask-password-api: drop unneeded parenthesesZbigniew Jędrzejewski-Szmek2020-03-021-2/+1
| |
| * core/execute: use return value from sockaddr_un_set_path(), remove duplicate ↵Zbigniew Jędrzejewski-Szmek2020-03-021-10/+10
| | | | | | | | check
| * homed,userdb: don't use sockaddr_un_set_path() on fixed addressesZbigniew Jędrzejewski-Szmek2020-03-022-10/+8
| | | | | | | | Let's use structured initialization and let the compiler do its job.
| * tree-wide: use the return value from sockaddr_un_set_path()Zbigniew Jędrzejewski-Szmek2020-03-0215-74/+93
| | | | | | | | | | | | | | | | | | It fully initializes the address structure, so no need for pre-initialization, and also returns the length of the address, so no need to recalculate using SOCKADDR_UN_LEN(). socklen_t is unsigned, so let's not use an int for it. (It doesn't matter, but seems cleaner and more portable to not assume anything about the type.)
| * test-sizeof: print size socklen_tZbigniew Jędrzejewski-Szmek2020-03-021-0/+3
| | | | | | | | | | | | It returns 32 bits, unsigned on amd64, so it's probably similar everywhere with glibc. But let's make the code generic, without assuming specific size or signedness.
| * journald: fix forwarding to syslogZbigniew Jędrzejewski-Szmek2020-03-021-5/+5
| | | | | | | | | | | | | | .msg_namelen was set to a bogus value before we actually stored the path in the the structure. sockaddr_un_set_path() returns the length, so just use that. Fixes #14799.
* | RequireMountsFor in systemd-nspawn should wait for machine mountKevin P. Fleming2020-03-021-1/+1
| | | | | | | | | | This patch modifies the RequireMountsFor setting in systemd-nspawn@.service to wait for the machine instance directory to be mounted, not just /var/lib/machines. Closes #14931
* | Merge pull request #14991 from yuwata/man-fix-typoYu Watanabe2020-03-022-1/+2
|\ \ | | | | | | assorted tiny fixes
| * | test-network: remove unnecessary dummy interfaceYu Watanabe2020-03-021-0/+1
| | |
| * | man: fix typoSusant Sahani2020-03-021-1/+1
| | |
* | | shared/logs-show: Remove unused OUTPUT_FOLLOWHATAYAMA Daisuke2020-03-022-70/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of the commit aae9a96d4b3a8562af9e8c6a23871b442645b954 removing --follow option in systemctl command, OUTPUT_FOLLOW has never been set anywhere. Let's remove it. The condition expression of the if-statement in show_journal() that refers to OUTPUT_FOLLOW now thus evaluates always to true. Hence, the call of sd_journal_wait() is in dead code, and the outer infinite for-loop is meaningless, which we remove as cleanup. There is no functional change by this commit.
* | | network: make Type=ether match based on iftypeYu Watanabe2020-03-0211-36/+74
|/ / | | | | | | | | | | This makes Type= can match the type shown in networkctl. Closes #14952.
* | Merge pull request #14990 from keszybz/nss-homed-fixYu Watanabe2020-03-023-3/+3
|\ \ | | | | | | Fix for lookup of groups defined by homed
| * | userdb: fix lookup of groups defined by homedZbigniew Jędrzejewski-Szmek2020-03-011-1/+1
| | |
| * | Fix two typosZbigniew Jędrzejewski-Szmek2020-03-012-2/+2
| |/
* | units: disable ProtectKernelLogs for machinedGuillaume Douézan-Grard2020-03-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | machined needs access to the host mount namespace to propagate bind mounts created with the "machinectl bind" command. However, the "ProtectKernelLogs" directive relies on mount namespaces to make the kernel ring buffer inaccessible. This commit removes the "ProtectKernelLogs=yes" directive from machined service file introduced in 6168ae5. Closes #14559.
* | random-seed: add missing header for GRND_NONBLOCK (#14988)Romain Naour2020-03-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | GRND_NONBLOCK has been introduced with the 3.17 kernel version [1] while adding getrandom(2) system call. The header missing_random.h is needed for random-seed.c when building with old toolchain, such Sourcery CodeBench ARM 2014.05 (kernel headers 3.13). Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/454255917 [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=c6e9d6f38894798696f23c8084ca7edbf16ee895
* | po: update Polish translationPiotr Drąg2020-03-021-37/+40
| |
* | l10n: update Czech TranslationAsciiWolf2020-03-021-35/+31
| |
* | Merge pull request #14983 from ssahani/dhcp-use-routes-14982Yu Watanabe2020-03-023-32/+55
|\ \ | | | | | | network: Allow to configure GW even if UseRoutes=false
| * | test-network: add a test case for [DHCPv4] UseRoutes=noYu Watanabe2020-03-022-0/+24
| | |
| * | network: Allow to configure GW even UseRoutes=falseSusant Sahani2020-03-021-32/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | When use UseRoutes=False so the DHCP request itself does not request for Classless Static Routes option. As a result, the DHCP server will only respond with a Router option. In this case since we are using the UseRoutes=False option the gateway that comes in via the router option does not get configured. This patch fixes theis behaviour.
* | | Merge pull request #14976 from keszybz/show-status-messageZbigniew Jędrzejewski-Szmek2020-03-0111-49/+68
|\ \ \ | |/ / |/| | core: fix message about show status state
| * | pid1: add new mode systemd.show-status=error and use it when 'quiet' is passedZbigniew Jędrzejewski-Szmek2020-03-016-14/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | systemd.show-status=error is useful for the case where people care about errors only. If people want to have a quiet boot, they most likely don't want to see all status output even if there is a delay in boot, so make "quiet" imply systemd.show-status=error instead of systemd.show-status=auto. Fixes #14976.
| * | pid1: when showing error status, do not switch to status=temporaryZbigniew Jędrzejewski-Szmek2020-03-017-12/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We would flip to status=temporary mode on the first error, and then switch back to status=auto after the initial transaction was done. This isn't very useful, because usually all the messages about successfully started units and not related to the original failure. In fact, all those messages most likely cause the information about the prime error to scroll off screen. And if the user requested quiet boot, there's no reason to think that they care about those success messages. Also, when logging about dependency cycles, treat this similarly to a unit error and show the message even if the status is "soft disabled" (before we wouldn't show it in that case).
| * | pid1: make cylon timeout significantly bigger when not showing any messagesZbigniew Jędrzejewski-Szmek2020-03-011-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we are booting with show-status=on, normally new status updates happen a few times per second. Thus, it is reasonable to start showing the cylon eye after 5 s, because that means a significant delay has happened. When we are running with show-status=off or show-status=auto (and no error had occured), the user is expecting maybe 15 to 90 seconds with no output (because that's usually how long the whole boot takes). So we shouldn't bother the user with information about a few seconds of delay. Let's make the timeout 25s if we are not showing any messages. Conversly, when we are outputting status messages, we can show the cylon eye with a shorter delay, now that we removed the connection to enablement status. Let's make this 2s, so users get feedback about delays more quickly.
| * | pid1: touch the /run/systemd/show-status just onceZbigniew Jędrzejewski-Szmek2020-03-011-6/+8
| | | | | | | | | | | | | | | | | | | | | We know if we created the file before, no need to repeat the operation. The state in /run should always match our internal state. Since we call manager_set_show_status() quite often internally, this saves quite a few pointless syscalls.
| * | pid1: when printing status message status, give reasonZbigniew Jędrzejewski-Szmek2020-03-014-15/+16
| | |
| * | core: fix message about show status stateZbigniew Jędrzejewski-Szmek2020-03-013-10/+15
| | | | | | | | | | | | | | | | | | | | | | | | We would say "Enabling" also for SHOW_STATUS_AUTO, which is actually "soft off". So just print the exact state to make things easier to understand. Also add a helper function to avoid repeating the enum value list. For #14814.
* | | rules.d: import the keyboard builtin instead of running itPeter Hutterer2020-03-011-6/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | RUN seems to be used primarily for historical reasons over the more immediate IMPORT command. As a side-effect, RUN also runs *after* all the rules have been processed which is not really what we want here - we expect the device to be updated immediately. Other rules that rely on accurate evdev axes should be able to assume the axes are already present. So let's use IMPORT here. For consistency, the second two rules are split across multiple lines as well.
* | | resolve: error handling improvementsYu Watanabe2020-03-011-9/+18
| | |
* | | Italian: removed spurious lines of old labelsDaniele Medri2020-03-011-7/+0
| | |
* | | italian: language updatesDaniele Medri2020-03-011-30/+96
| |/ |/|
* | Merge pull request #14966 from keszybz/journalctl-facilitiesYu Watanabe2020-03-013-1/+89
|\ \ | | | | | | journalctl: filtering by facility
| * | journalctl: implement --facility=fooZbigniew Jędrzejewski-Szmek2020-02-292-0/+88
| | | | | | | | | | | | Fixes #9716.
| * | basic/string-table: avoid crash when table is sparseZbigniew Jędrzejewski-Szmek2020-02-271-1/+1
| | | | | | | | | | | | | | | Generated _from_string() would crash when invoked on a table with some holes.
* | | hwdb: Add Medion Akoya E1239T MD60568 to 60-sensor.hwdbHans de Goede2020-02-291-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | Unlike newer Medion Akoya E* models for which we have a generic wildcard match, this model uses a somewhat older KIOX0009 accelerometer. Not only does our generic catch all not match, we also need a different matrix for this model, so add a model-specific entry for it.
* | | homed: fix typoYu Watanabe2020-02-296-30/+30
| | |
* | | Merge pull request #14979 from keszybz/enable-pstore-by-defaultYu Watanabe2020-02-293-9/+11
|\ \ \ | | | | | | | | Enable pstore by default
| * | | presets: enable systemd-pstore.service by defaultZbigniew Jędrzejewski-Szmek2020-02-291-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It has no effect is the pstore is not used, and prevents the non-volatile storage from filling up if is used by the kernel. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952767
| * | | man: add .service suffix to systemd-pstore(8)Zbigniew Jędrzejewski-Szmek2020-02-292-5/+5
| | | | | | | | | | | | | | | | | | | | That is the pattern that we always use with executables not in $PATH.
| * | | man: tweak markup in systemd-pstore.service(8)Zbigniew Jędrzejewski-Szmek2020-02-291-4/+4
| | | |
* | | | Revert "namespace: fix MAC labels of /dev when PrivateDevices=yes"Topi Miettinen2020-02-297-40/+12
| | | | | | | | | | | | | | | | This reverts commit e6e81ec0a56861b905db975fc32c83e2f2faca7d.
* | | | pid1: do not fail if we get EPERM while setting up network nameZbigniew Jędrzejewski-Szmek2020-02-291-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In a user namespace container: Feb 28 12:45:53 0b2420135953 systemd[1]: Starting Home Manager... Feb 28 12:45:53 0b2420135953 systemd[21]: systemd-homed.service: Failed to set up network namespacing: Operation not permitted Feb 28 12:45:53 0b2420135953 systemd[21]: systemd-homed.service: Failed at step NETWORK spawning /usr/lib/systemd/systemd-homed: Operation not permitted Feb 28 12:45:53 0b2420135953 systemd[1]: systemd-homed.service: Main process exited, code=exited, status=225/NETWORK Feb 28 12:45:53 0b2420135953 systemd[1]: systemd-homed.service: Failed with result 'exit-code'. Feb 28 12:45:53 0b2420135953 systemd[1]: Failed to start Home Manager. We should treat this similarly to the case where network namespace are not supported at all. https://bugzilla.redhat.com/show_bug.cgi?id=1807465
* | | | execute: Make '+' exec prefix ignore PrivateTmp=yesNate Jones2020-02-295-14/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The man pages state that the '+' prefix in Exec* directives should ignore filesystem namespacing options such as PrivateTmp. Now it does. This is very similar to #8842, just with PrivateTmp instead of PrivateDevices.
View Lorry Controller Status