Re: [systemd-devel] About the exit of systemd-udevd
On Tue, Apr 14, 2015 at 4:47 PM, Tom Yan tom.t...@gmail.com 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 systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] About the exit of systemd-udevd
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?
Attached is a script for testing. I think any arbitrary udev rule
could be used for testing. For example I used:
ATTR{devpath}==13, ATTR{power/wakeup}==enabled/disabled
trigger.sh
Description: Bourne shell script
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
