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 [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
