On Tue, Apr 14, 2015 at 4:47 PM, Tom Yan <[email protected]> wrote: > Under certain conditions, I discovered that commands like `udevadm > control --exit` or `systemctl stop systemd-udevd` (with the sockets > stopped beforehand) will kill udevd before it finish its jobs which > triggered by `udevadm trigger` (I presume applying a written udev rule > is one of them). > > Is this acceptable/expected? If so, is there any way to guarantee the > jobs is done before it gets killed?
It is expected, udevd will finish everything that is currently already running and do a clean shutdown, but not process any new events which might be triggered and pending. Kay _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
