Hi Am 23.06.2018 um 10:40 schrieb Sven Joachim: > ,---- > | $ systemctl status systemd-udevd.service > | ● systemd-udevd.service - udev Kernel Device Manager > | Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; > vendor preset: enabled) > | Active: failed (Result: exit-code) since Sat 2018-06-23 10:16:18 CEST; > 9min ago > | Docs: man:systemd-udevd.service(8) > | man:udev(7) > | Main PID: 4230 (code=exited, status=127) > | > | Jun 23 10:16:18 pavil systemd[1]: systemd-udevd.service: Service has no > hold-off time, scheduling restart. > | Jun 23 10:16:18 pavil systemd[1]: systemd-udevd.service: Scheduled restart > job, restart counter is at 5. > | Jun 23 10:16:18 pavil systemd[1]: Stopped udev Kernel Device Manager. > | Jun 23 10:16:18 pavil systemd[1]: systemd-udevd.service: Start request > repeated too quickly. > | Jun 23 10:16:18 pavil systemd[1]: systemd-udevd.service: Failed with result > 'exit-code'. > | Jun 23 10:16:18 pavil systemd[1]: Failed to start udev Kernel Device > Manager. > | Jun 23 10:16:18 pavil systemd[1]: > /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' > in secti\ > | on 'Service' > | Jun 23 10:16:18 pavil systemd[1]: > /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, > ignoring: @s\ > | ystem-service > `----
Hm, it seems it is the addition of SystemCallFilter=@system-service @module @raw-io to systemd-udevd.service which triggers the failure. The newly introduced PrivateMounts= is properly ignored by the older systemd. @system-service is a new seccomp call set that was introduced in v239. I first tried removing that is not sufficient to make udevd start though with systemd v238. I had to comment out the whole SystemCallFilter= line. I guess bumping the Breaks is indeed the way to go. Thanks for the bug report. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
