summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | sd-bus: 'ret' parameter to sd_bus_query_sender_creds() is not optional, ↵Lennart Poettering2020-12-151-0/+1
| | | | | | | | | | | | check for it
| * | sd-bus: make credential acquisition more gracefulLennart Poettering2020-12-152-7/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far when asked for augmented bus credentials and the process was already gone we'd fail fatally. Let's make this graceful instead, and never allow augmenting fail due to PID having vanished — unless the augmenting is the explicit and only purpose of the requested operation. This should be safe as clients have to explicitly query the acquired creds anyway and handle if they couldn't be acquired. Moreover we already handle permission problems gracefully, thus clients must be ready to deal with missing creds. This is useful to make selinux authorization work for short-lived client proceses. PReviously we'd augment creds to have more info to log about (the selinux decision would not be based on augmented data however, because that'd be unsafe), and would fail if we couldn't get it. Now, we'll try to acquire the data, but if we cannot acquire it, we'll still do the selinux check, except that logging will be more limited.
| * | firstboot: clean-up the copied hostname, not argv[] directly, as that's uglyLennart Poettering2020-12-151-1/+1
| | |
| * | hostname-setup: clarify that failures reading /etc/hostname are ignoredLennart Poettering2020-12-151-6/+5
| | |
| * | hostname-util: flagsify hostname_is_valid(), drop machine_name_is_valid()Lennart Poettering2020-12-1530-109/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's clean up hostname_is_valid() a bit: let's turn the second boolean argument into a more explanatory flags field, and add a flag that accepts the special name ".host" as valid. This is useful for the container logic, where the special hostname ".host" refers to the "root container", i.e. the host system itself, and can be specified at various places. let's also get rid of machine_name_is_valid(). It was just an alias, which is confusing and even more so now that we have the flags param.
| * | hostname-util: explain what 'LDH' isLennart Poettering2020-12-151-0/+2
| | |
| * | logs-show: drop redundant validation of machine nameLennart Poettering2020-12-151-3/+0
| | | | | | | | | | | | | | | | | | The immediately following container_get_leader() call validate the name anyway, no need to twice exactly the same way twice immediately after each other.
| * | machine: drop really old kdbus left-overLennart Poettering2020-12-151-1/+1
| | | | | | | | | | | | | | | The "x-machine-kernel" dbus address has been removed a long time ago, hence don't generate it either.
| * | sd-bus: use SOCK_CLOEXEC on one more socketLennart Poettering2020-12-151-1/+1
| | |
* | | busctl: add a timestamp to the output of the busctl monitor commandd0327472020-12-162-0/+17
| | |
* | | Merge pull request #17908 from ddstreet/dhcpv4_rfc2131_intervalsYu Watanabe2020-12-162-88/+80
|\ \ \ | |_|/ |/| | Fix dhcpv4 renew/rebind intervals to match rfc2131
| * | test-network: increase wait_online timeout to handle longer dhcpv4 transient ↵Dan Streetman2020-12-141-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | timeout Previous commits changed the dhcpv4 retransmission algorithm to be slightly slower, changing the amount of time it takes to notify systemd-networkd that the dhcpv4 configuration has (transiently) failed from around 14 second up to 28 seconds. Since the test_dhcp_client_with_ipv4ll_without_dhcp_server test configures an interface to use dhcpv4 without any operating dhcpv4 server running, it must increase the amount of time it waits for the test interface to reach degraded state.
| * | sd-dhcp-client: correct retransmission timeout to match RFCDan Streetman2020-12-141-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the retransmission timeout algorithm for requests other than RENEW and REBIND. Previously, the retransmission timeout started at 2 seconds, then doubling each retransmission up to a max of 64 seconds. This is changed to match what RFC2131 section 4.1 describes, which skips the initial 2 second timeout and starts with a 4 second timeout instead. Note that -1 to +1 seconds of random 'fuzz' is added to each timeout, in previous and current behavior. This change is therefore slightly slower than the previous behavior in attempting retransmissions when no server response is received, since the first transmission times out in 4 seconds instead of 2. Since TRANSIENT_FAILURE_ATTEMPTS is set to 3, the previous length of time before a transient failure was reported back to systemd-networkd was 2 + 4 + 8 = 14 seconds, plus, on average, 3 seconds of random 'fuzz' for a transient failure timeout between 11 and 17 seconds. Now, since the first timeout starts at 4, the transient failure will be reported at 4 + 8 + 16 = 28 seconds, again plus 3 random seconds for a transient failure timeout between 25 and 31 seconds. Additionally, if MaxAttempts= is set, it will take slightly longer to reach than with previous behavior.
| * | sd-dhcp-client: correct dhcpv4 renew/rebind retransmit timeoutsDan Streetman2020-12-141-13/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the request timeout algorithm specified in RFC2131 section 4.4.5 for handling timed out RENEW and REBIND requests. This changes behavior, as previously only 2 RENEW and 2 REBIND requests were sent, no matter how long the lease lifetime. Now, requests are send according to the RFC, which results in starting with a timeout of 1/2 the t1 or t2 period, and halving the timeout for each retry down to a minimum of 60 seconds. Fixes: #17909
| * | sd-dhcp-client: simplify dhcp4 t1/t2 parsingDan Streetman2020-12-141-57/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parsing of the dhcpv4 lease lifetime, as well as the t1/t2 times, is simplified by this commit. This differs from previous behavior; previously, the lease lifetime and t1/t2 values were modified by random 'fuzz' by subtracting 3, then adding a random number between 0 and (slightly over) 2 seconds. The resulting values were therefore always between 1-3 seconds shorter than the value provided by the server (or the default, in case of t1/t2). Now, as described in RFC2131, the random 'fuzz' is between -1 and +1 seconds, meaning the actual t1 and t2 value will be up to 1 second earlier or later than the server-provided (or default) t1/t2 value. This also differs in handling the lease lifetime, as described above it previously was adjusted by the random 'fuzz', but the RFC does not state that the lease expiration time should be adjusted, so now the code uses exactly the lease lifetime as provided by the server with no adjustment.
| * | sd-dhcp-client: add RFC2131 retransmission detailsDan Streetman2020-12-141-0/+32
| | | | | | | | | | | | | | | | | | RFC2131, providing the details for dhcpv4, has specific retransmission intervals that it outlines. This adds functions to compute the timeouts as the RFC describes.
| * | sd-dhcp-client: track dhcp4 t1, t2, expire timesDan Streetman2020-12-141-27/+27
| | | | | | | | | | | | Add fields to dhcp4 client to track t1, t2, and lease expiry times
| * | sd-dhcp-client: don't log timeouts if already expiredDan Streetman2020-12-141-8/+9
| | |
* | | journalctl: don't skip the entries that have the same seqnumshenyangyang42020-12-152-3/+8
| |/ |/| | | | | | | These two judgement can't judge that two entries are repeating fully. So i think seqnum is needed to make full judgement.
* | Fix review comments in added debug log.Gaurav2020-12-151-7/+3
| |
* | Fix build warning.Gaurav2020-12-151-0/+1
| |
* | Handle escape characters in interface nameGaurav2020-12-151-1/+8
| | | | | | Updated the patch as per review comments.
* | Detect special character in dbus interface nameGaurav2020-12-151-1/+3
| | | | | | | | Added debug log to detect special character in dbus interface names. Helps to detect a case mentioned in https://github.com/systemd/systemd/issues/14636
* | Translated using Weblate (German)Fabian Affolter2020-12-151-10/+11
| | | | | | | | | | | | | | | | Currently translated at 61.4% (115 of 187 strings) Co-authored-by: Fabian Affolter <mail@fabian-affolter.ch> Translate-URL: https://translate.fedoraproject.org/projects/systemd/master/de/ Translation: systemd/master
* | resolved: create stub-resolv.conf symlink with correct security labelOndrej Mosnacek2020-12-151-1/+2
| | | | | | | | | | | | | | Use symlink_atomic_label() instead of symlink_atomic() as the symlink may need a different label than the parent directory. Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
* | Merge pull request #17977 from yuwata/namespace-mount-procfs-follow-upYu Watanabe2020-12-151-3/+2
|\ \ | | | | | | core/namespace: do not ignore non-EPERM mount error
| * | Revert "core/namespace: ignore ENOENT for /proc/sys/kernel/domainname and ↵Yu Watanabe2020-12-151-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hostname" This reverts commit 0ebc9f23faf5586f8a9250c3be08773eb3f8d2da. With the previous commit, these files should always exist. Closes #17979.
| * | core/namespace: do not ignore non-EPERM mount errorYu Watanabe2020-12-151-1/+2
| | | | | | | | | | | | Follow-up for 61f8a7bd3e20222617fc59f398071daf2af86f96.
* | | efi: Only use arm flags if supportedAndrew Balmos2020-12-151-1/+7
| | | | | | | | | | | | Support gcc 8 on arm
* | | Merge pull request #17936 from keszybz/more-nss-loggingYu Watanabe2020-12-153-89/+100
|\ \ \ | | | | | | | | Add debug logging for varlink
| * | | varlink: add debug loggingZbigniew Jędrzejewski-Szmek2020-12-141-84/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When something fails, we need some logs to figure out what happened. This is primarily relevant for connection errors, but in general we want to log about all errors, even if they are relatively unlikely. We want one log on failure, and generally no logs on success. The general idea is to not log in static functions, and to log in the non-static functions. Non-static functions which call other functions may thus log or not log as appropriate to have just one log entry in the end.
| * | | basic/log: add debug-level log_oom() variantZbigniew Jędrzejewski-Szmek2020-12-112-5/+5
| | | | | | | | | | | | | | | | This is useful for contexts where only debug-level messages are allowed.
* | | | timesync: Make delaying attempts to contact servers configurableSusant Sahani2020-12-155-8/+25
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``` ❯ 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 ```
* | | Merge pull request #17960 from yuwata/network-log-routing-policy-ruleLuca Boccassi2020-12-142-118/+71
|\ \ \ | | | | | | | | network: introduce log_routing_policy_rule()
| * | | network: use netlink_message_read_in_addr_union() where applicableYu Watanabe2020-12-141-52/+17
| | | |
| * | | network: introduce log_routing_policy_rule_debug()Yu Watanabe2020-12-141-33/+26
| | | |
| * | | network: introduce routing_policy_rule_equal()Yu Watanabe2020-12-141-1/+11
| | | |
| * | | network: make routing_policy_rule_remove() take Manager instead of LinkYu Watanabe2020-12-142-34/+19
| | | | | | | | | | | | | | | | As routing policy rules are managed by Manager.
* | | | Merge pull request #17959 from yuwata/network-log-addressLuca Boccassi2020-12-141-49/+41
|\ \ \ \ | | | | | | | | | | network: introduce log_address_debug()
| * | | | network: make address_drop() accept NULLYu Watanabe2020-12-141-3/+3
| | | | |
| * | | | network: introduce log_address_debug()Yu Watanabe2020-12-141-47/+39
| |/ / /
* | | | Merge pull request #17958 from yuwata/network-route-logLuca Boccassi2020-12-141-167/+85
|\ \ \ \ | | | | | | | | | | network: introduce log_route_debug()
| * | | | network: merge manager_drop_routes() and manager_drop_foreign_routes()Yu Watanabe2020-12-141-28/+13
| | | | |
| * | | | network: introduce log_route_debug()Yu Watanabe2020-12-141-82/+50
| | | | |
| * | | | network: use netlink_message_read_in_addr_union() where applicableYu Watanabe2020-12-141-57/+22
| |/ / /
* | | | core: detect_container() may return negative errnoYu Watanabe2020-12-141-1/+1
| |_|/ |/| |
* | | time-util: fix typoYu Watanabe2020-12-141-1/+1
| | |
* | | core/namespace: use existing /proc when not enough priviledgeYu Watanabe2020-12-141-27/+34
| | | | | | | | | | | | Fixes #17860.
* | | core/namespace: ignore ENOENT for /proc/sys/kernel/domainname and hostnameYu Watanabe2020-12-141-0/+2
|/ / | | | | | | | | | | If they do not exist, hostname or domainname cannot be modified. So, it is ok. Fixes #17866, especially https://github.com/systemd/systemd/issues/17866#issuecomment-744118614.
* | Update TODOLennart Poettering2020-12-141-0/+2
| |
View Lorry Controller Status