summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Revert "ci: temporarily pin Arch repositories to glibc 2.32-5"revert-18515-temporarily-pin-arch-reposFrantisek Sumsal2021-02-091-9/+0
| | | | This reverts commit 67c972c610de61789d1b6560d28340f70d4b1196.
* log: do not use uninitialized valueYu Watanabe2021-02-091-1/+3
| | | | Follow-up for 85cf96e3f567cd51f79d671bbf3559550fdd67b7.
* ci: temporarily pin Arch repositories to glibc 2.32-5Frantisek Sumsal2021-02-091-0/+9
| | | | | | | | | glibc 2.33-3 shipped on 2021-02-06 breaks running Arch containers on systems with older kernels (like Ubuntu Focal). Until the issue is resolved, let's pin the Arch repositories to glibc 2.32-5 to mitigate the annoying CI fails. See: https://bugs.archlinux.org/task/69563
* Merge pull request #18346 from yuwata/hostnamectl-try-to-set-transient-hostnameZbigniew Jędrzejewski-Szmek2021-02-096-188/+386
|\ | | | | hostnamectl: try to set transient hostname even if setting static or pretty hostname failed
| * hostnamectl: use TableYu Watanabe2021-02-091-49/+145
| |
| * hostnamectl: show hint when user try to set transient hostname but static ↵Yu Watanabe2021-02-093-5/+33
| | | | | | | | hostname is already used
| * hostname: use free_and_strdup_and_warn()Yu Watanabe2021-02-091-2/+2
| |
| * hostname: re-read file later when failed to update fileYu Watanabe2021-02-091-8/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, even when writing e.g. /etc/hostname fails, the static hostname in Context is not restored. So, the subsequent call of the same method succeeds: ``` $ sudo chattr +i /etc/hostname $ sudo hostnamectl --static set-hostname aaa Could not set static hostname: Access denied $ echo $? 1 $ sudo hostnamectl --static set-hostname aaa $ echo $? 0 ``` This makes when updating file is failed, the saved stat is cleared. So, the static hostname or machine information in the context are always consistent to the corresponding files.
| * hostnamectl: unset pretty hostname only when no target is specifiedYu Watanabe2021-02-091-1/+1
| |
| * hostnamectl: try to set transient hostname even if updating static or pretty ↵Yu Watanabe2021-02-091-13/+44
| | | | | | | | | | | | | | | | hostname failed If no target (--pretty, --static, or --transient) is specified, then let's try to set transient hostname even if setting static or pretty hostname failed. This may be useful for read-only filesystem.
| * hostname: introduce two bus errors for updating fileYu Watanabe2021-02-093-0/+12
| |
| * bus-error: align error definitionsYu Watanabe2021-02-091-104/+105
| |
| * hostnamectl: improve log message on failureYu Watanabe2021-02-091-10/+10
| |
* | test-network: support protocol and linkdown flag for ff00::/8 routeYu Watanabe2021-02-091-4/+4
| | | | | | | | Fixes #18507.
* | network: Delay addition of IPv6 Proxy NDP addressesKevin P. Fleming2021-02-092-5/+11
|/ | | | | | | | Setting of IPv6 Proxy NDP addresses must be done at the same time as static addresses, static routes, and other link attributes that must be configured when the link is up. Doing this ensures that they are reconfigured on the link if the link goes down and returns to service.
* hwdb: add axis overrides for the Dell Latitude E5510 TouchPad (#18493)Gablegritule2021-02-091-0/+7
| | | | I added an entry for Dell Latitude E5510 TouchPad to set up the true size of the TouchPad (the size is currently over-estimated)
* Merge pull request #18478 from mrc0mmand/fix-TEST-06Frantisek Sumsal2021-02-083-1/+3
|\ | | | | TEST-06-SELINUX fixes
| * test: add a custom SELinux file contextFrantisek Sumsal2021-02-052-0/+2
| | | | | | | | | | | | | | | | | | Since the test suite overhaul, the test units are now under /usr/lib/systemd/tests/testdata/tetsuite-06.units with system_u:object_r:lib_t context. This causes an AVC denial, since the systemd unit files are expected to have the system_u:object_r:systemd_unit_file_t context. Let's fix this by using a custom file context definition.
| * test: clean the module build dir before compiling itFrantisek Sumsal2021-02-051-1/+1
| | | | | | | | | | otherwise the module won't compile & load after autorelabel reboot, since the target is already built.
* | Merge pull request #18375 from yuwata/cli-tools-also-read-kernel-command-lineZbigniew Jędrzejewski-Szmek2021-02-0884-106/+210
|\ \ | | | | | | tree-wide: make CLI tools also read kernel command line when run as service
| * | log: skip reading the kernel command line if the process is invoked by a scriptYu Watanabe2021-02-011-4/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CLI tools may be used in a script. E.g., a script for monitoring a service may use `systemctl`. Previously, if the kernel command line has e.g. systemd.log-level=debug, then systemctl in the script produces debugging logs when the script is invoked by a .service unit, but does not when the script is running in a terminal. Then, https://github.com/systemd/systemd/pull/18281#discussion_r561697482, > I expect users to be (negatively) surprised. In the previous commit, $SYSTEMD_EXEC_PID= is introduced. Then, we can now detect whether a command is directly invoked by systemd or through a script. Let's skip reading the kernel command line when a command is invoked through a script.
| * | import,home: update $SYSTEMD_EXEC_PID= if it is setYu Watanabe2021-02-012-0/+9
| | | | | | | | | | | | | | | The subsequent execv() or execl() always calls tools provided by systemd. So, it is safe to update the variable.
| * | core: also set $SYSTEMD_EXEC_PID= for generatorsYu Watanabe2021-02-013-7/+16
| | |
| * | env-util: introduce env_update_systemd_exec_pid()Yu Watanabe2021-02-013-0/+63
| | | | | | | | | | | | Will be used in later commits.
| * | test: use test_setup_logging() in test-env-utilYu Watanabe2021-02-011-0/+3
| | |
| * | core: set $SYSTEMD_EXEC_PID= environment variable for executed commandsYu Watanabe2021-02-012-1/+17
| | | | | | | | | | | | | | | It may be useful to detect a command is directly executed by systemd manager, or indirectly as a child of another process.
| * | tree-wide: enable colorized logging for daemons when run in consoleYu Watanabe2021-02-0172-85/+72
| | | | | | | | | | | | It may be useful when debugging daemons.
| * | log: make tools also read the kernel command line when run as a serviceYu Watanabe2021-02-015-13/+8
| | | | | | | | | | | | | | | | | | | | | | | | This effectively reverts 41d1f469cf10f5f3e9cb4f4853ace9b0cfe5beae. Before this, e.g., `networkctl reload` invoked by `systemctl reload systemd-networkd.service` does not produce debugging logs even if systemd.log-level=debug is set. This fixes the issue.
* | | Merge pull request #18331 from yuwata/test-udev-event-spawnZbigniew Jędrzejewski-Szmek2021-02-085-34/+165
|\ \ \ | | | | | | | | udev: add tests for udev_event_spawn()
| * | | sd-event: retrieve more events when epoll_wait() returns number equivalent ↵Yu Watanabe2021-02-021-14/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to the buffer size When epoll_wait() returns number equivalent to the buffer size, there may exist remaining events which may have higher priority. To make priority sorting correctly, let's retrieve all events.
| * | | test: add test for udev_event_spawn()Yu Watanabe2021-02-022-0/+114
| | | |
| * | | udev: ignore OOM error in on_spawn_io()Yu Watanabe2021-02-021-3/+3
| | | |
| * | | udev: use strv_split_newlines() to parse result of spawned commandYu Watanabe2021-02-011-8/+9
| | | |
| * | | udev: add debugging logs in spawn_wait()Yu Watanabe2021-02-011-9/+9
| | | |
* | | | Use correct config parser for MountAPIVFS (#18501)Antonius Frie2021-02-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As far as I can see, at some point the parser function for MountAPIVFS was changed from the generic bool parser to a custom implementation, to allow the context to keep track of whether MountAPIVFS had been set explicitly. If not, exec_context_get_effective_mount_apivfs would fall back to a default value. However, the corresponding entry in the big parser table wasn't updated, meaning that the old bool parser was still used, meaning that context->mount_apivfs_set remained at its default value of false, meaning that the default value was always used and the config option was effectively ignored. Fix for 5e98086d1629f5c5b73645ba2568de4b09b7d958.
* | | | hwdb: add Acecad Flair / Pentagram Quadpen (#18443)cprn2021-02-071-0/+9
| | | |
* | | | Merge pull request #18490 from keszybz/prettify-update-dbus-docsLuca Boccassi2021-02-061-8/+14
|\ \ \ \ | | | | | | | | | | Prettify update-dbus-docs
| * | | | update-dbus-docs: use color in summaryZbigniew Jędrzejewski-Szmek2021-02-061-1/+6
| | | | |
| * | | | update-dbus-docs: say "MODIFIED" not "OUTDATED"Zbigniew Jędrzejewski-Szmek2021-02-061-7/+8
| | |_|/ | |/| | | | | | | | | | | | | | | | | | When executed in test mode, "OUTDATED" is appropriate. But when executed to actually update the text, after the tool executes, those pages are the opposite, not outdated.
* | | | copy: use stat_verify_directory() where appropriateLennart Poettering2021-02-061-4/+8
| | | |
* | | | man: fix misspellings of "NameSeviceSwitch"Julia Cartwright2021-02-062-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixup NameSeviceSwitch -> NameServiceSwitch spelling error in documentation. Found through inspection of documentation.
* | | | Translations update from Weblate (#18485)Weblate (bot)2021-02-051-33/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Translated using Weblate (Swedish) Currently translated at 100.0% (189 of 189 strings) Translation: systemd/main Translate-URL: https://translate.fedoraproject.org/projects/systemd/master/sv/ Co-authored-by: Göran Uddeborg <goeran@uddeborg.se>
* | | | github: ask for systemd version in RFE formLennart Poettering2021-02-051-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | It happens too often that what people ask for already is implemented. Let's help cut the noise a bit, and make people check things first hopefully, and at least make it either for us to detect such cases.
* | | | resolved: suppress ifindex info in varlink JSON responses if zeroLennart Poettering2021-02-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we don't have ifindex info, don't set the field for it. We already do that for parsed IP address replies, let's do it for all cases: it's a bit nicer to suppress the ifindex prop if it doesn't apply than to pass it invalid. This is the other side of #18482, i.e. fixes things so that the parser doesn't get tripped up by this. (This too makes a problem go away we should track down properly, i.e. figure out how the ifindex got lost in https://github.com/systemd/systemd/pull/17823#issuecomment-742439422 )
* | | | Merge pull request #18482 from poettering/resolved-nss-varlink-ifindex-fixLennart Poettering2021-02-061-2/+2
|\ \ \ \ | | | | | | | | | | nss-resolve: handle zero ifindex reply from server
| * | | | nss-resolve: shortcut fixing of ifindex if it's zero anywayLennart Poettering2021-02-051-1/+1
| | | | |
| * | | | nss-resolve: accept zero ifindex when parsing resolved replyLennart Poettering2021-02-051-1/+1
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sometimes a reply isn't associated to any specific interface, it might be a general truth (for example served from /etc/hosts or so). In this case the server might pass ifindex == 0. Accept that. https://github.com/systemd/systemd/pull/17823#issuecomment-742439422
* | | | Merge pull request #18318 from yuwata/network-route-table-nameLennart Poettering2021-02-058-107/+226
|\ \ \ \ | | | | | | | | | | network: RouteTable= improvements
| * | | | test: add tests for RouteTable= settingYu Watanabe2021-02-031-0/+50
| | | | |
| * | | | network: use defined route table name in debug logsYu Watanabe2021-02-036-66/+117
| | | | | | | | | | | | | | | | | | | | | | | | | And rename route_table_from_string_full() to manager_get_route_table_from_string().
View Lorry Controller Status