Lennart Poettering
Lennart Poettering
my educated guess is that NM has bluetooth support, and hence wants bluez to start first. but for some reason bluez is broken for you, and times out, which then...
I cannot tell you why bluez times out. Try figuring that out.
> FYI, even with `AT_HANDLE_FID` the handle from `name_to_handle_at` was noisy on btrfs and tmpfs when the parent directory got updated. We should probably also try to set `AT_HANDLE_MNT_ID_UNIQUE` for...
hmm, you are using the inode nr, but that's not a great identifier? why not use the name_to_handle_at() FID handle?
hmm, if i grok this properly, then you are formatting everything as string, and compare things as string. given the complexity of the data, and the history (i.e. two different...
> The name_to_handle_at() value (even with FID) changed directly during the systemd-sysext run for the parent directory `/etc/extensions/` probably because the directory got a new timestamp. I didn't look into...
hmm, is there anything VRF specific in this patch? it can bind a service to any iface, no, regardless if vrf or not
this really needs a CI test, maybe add to test/units/TEST-07-PID1.exec-context.sh where RestrictFileSystems= is tested too
> Would you prefer to turn this into something more generic, that allows binding to any interface, or to limit it to VRF interfaces only, probably when calling `rtnl_resolve_interface()` on...
also needs documention in man/systemd.resource-control.xml