Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-08-26 | units: remove udev control socket when systemd stops the socket unit (#4039) | Michal Sekletar | |
Mere presence of the socket in the filesystem makes udev_queue_get_udev_is_active() return that udev is running. Note that, udev on exit doesn't unlink control socket nor does systemd. Thus socket stays around even when both daemon and socket are stopped. This causes problems for cryptsetup because when it detects running udev it launches synchronous operations that *really* require udev. This in turn may cause blocking and subsequent timeout in systemd-cryptsetup on reboot while machine is in a state that udev and its control socket units are stopped, e.g. emergency mode. Fixes #2477 | |||
2013-08-17 | udev: replace CAP_MKNOD by writable /sys condition | Kay Sievers | |
2013-03-25 | units: and also, order all early-boot sockets before sockets.target | Lennart Poettering | |
2012-07-02 | units: Rename systemd-udev.service to systemd-udevd.service | Colin Guthrie | |
This naming convention is more inline with other systemd daemon unit names (systemd-logind.service, systemd-localed.service etc) The companion .socket units have also been renamed, however the -trigger and -settle units keep their current name as these are not directly related to daemon process itself. |