| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The test binary has two modes: in the default argument-less mode, it
just checks that "root" can be resolved. When invoked manually, a root
prefix and user/group names can be specified.
|
|\
| |
| | |
network: cleanups for radv and ndisc
|
| |
| |
| |
| | |
Also adjust log levels.
|
| | |
|
|\ \
| | |
| | | |
Improvements to udev logging and related code
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
We use LOG_PRI() in all log_*() functions, so let's do that here too for
consistency. Effectively this doesn't change anything since we only use
LOG_{INFO,DEBUG,...} as the argument.
|
| | |
| | |
| | |
| | |
| | |
| | | |
E.g. udevadm test prints "Invalid inotify descriptor." which is
meaningless without any context. I think it should be OK to call udev_watch_end()
from a cleanup path without any warning (even at debug level).
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
strjoin should be faster for string concatenation.
Also drop "_"-prefix from function prototypes.
|
| | |
| | |
| | |
| | |
| | | |
We shouldn't say "ignoring" when running a program because the result is used for
the match/nomatch result of the rule.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
967de8faceaa83c11a1215515cb135d7a8c0c32c added a note that I found very hard
to understand. Reword it, and also describe how IMPORT and PROGRAM are different
from RUN.
Minor markup adjustements too.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is no reason to consider this wrong. In fact one could argue that +=
is more appropriate, because we always add to options, and not replace previous
assignments. If we output a debug message, we implicitly ask people to "fix" this,
and we shouldn't.
Also, all our rules use += right now.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Udev logs are full of messages about wrong operator type:
...
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:54 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:57 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:60 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:63 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:66 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:67 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:93 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:107 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:110 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-storage.rules:113 IMPORT key takes '==' or '!=' operator, assuming '=='.
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
/usr/lib/udev/rules.d/60-persistent-v4l.rules:7 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-v4l.rules:9 IMPORT key takes '==' or '!=' operator, assuming '=='.
/usr/lib/udev/rules.d/60-persistent-v4l.rules:16 IMPORT key takes '==' or '!=' operator, assuming '=='.
...
The warning was downgraded in f0beb6f816035e438d684cc52ae76fc4a44fc197, but I
think it should be removed altogether. IMPORT{program}="asdf" seems like an
obvious way to write this, and people don't expect to have to write "==".
So let's just allow any operator.
|
| |/
|/|
| |
| | |
Fixes #16489
|
| | |
|
|\ \
| | |
| | | |
Follow-up for comments on #15891
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The kernel interface requires setting up read-only bind-mounts in
two steps, the bind first and then a read-only remount.
Fix nspawn-mount, and cover this case in the integration test.
Fixes #16484
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
two coverity fixes
|
| | |
| | |
| | |
| | | |
Fixes: coverity 1430462
|
| | |
| | |
| | |
| | | |
Fixes: coverity 1430459
|
|\ \ \
| | | |
| | | | |
man: three minor fixes to environment.d/ man page
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This only sets the environment for user *services*, it has no effect on
sessions, as those get an env block set up by whatever program sets them
up and not systemd.
|
|\ \ \ \
| |/ / /
|/| | | |
network: fix two minor races in DHCP4 handling
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If the SD_IPV4ACD_EVENT_BIND event happens before all routes are
assigned, then the link stuck in configuring state.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The lease lost may happen during renewing address. If it happens,
assertion hits in dhcp4_release_old_lease().
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
enforced mode"
This reverts commit 257188f80ce1a083e3a88b679b898a73fecab53b.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Follow-up for ceaec54a3c8366e81863a7d0d9c1f1d9f09960e1.
Hopefully fixes #16299.
|
| | |
| | |
| | |
| | |
| | | |
We typically don't log above LOG_WARNING about issues we then go on to
ignore. Do so here, too
|
|/ / |
|
| |
| |
| |
| | |
We miscounted here, and would hit an assert once too early.
|
|/ |
|
| |
|
|\
| |
| | |
network: about xxx_configured flags
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If DHCP4 client lost a lease, and then soon acquire new lease, then
the removal of the old address may not be completed. If that happens,
and the new and old addresses are the same, then the new address will be
considered as a foreign address. Such a situation can occur when the
DHCP4 server is restarted.
This makes networkd wait for the removal of the old address when a new
lease is acquired.
This also makes the link in configuring state when renewing address.
|
| |
| |
| |
| |
| |
| | |
link_request_set_routing_policy_rule()
It will be called in link_request_set_nexthop() or serveral handlers().
|
| |
| |
| |
| |
| |
| | |
link_request_set_routes() or route_handler()
Then we can drop static_routes_ready() flag.
|
| |
| |
| |
| |
| |
| |
| |
| | |
When DHCP6 and RA are enabled, and RA does not provide any addresses,
then link may become configured state even if no address is assigned,
due to the time-lag between RA completion and DHCP reply.
This makes if DHCP is explicitly enabled, then link must have at least
one valid address to be in the configured state.
|
| | |
|
| |
| |
| |
| | |
Follow-up for c24c83dc67a63c88b0a537f4fa7f605b1fcbac39.
|
| | |
|