7375b3c4871861f100860ea4c2848e66b60e6ca4 |
|
22-Apr-2015 |
Nir Soffer <nirsof@gmail.com> |
udev: Fix ping timeout when settle timeout is 0
When running udevadm settle --timeout=0, the ping always times out, and
udevadm will return 0 without checking the queue state.
(David: Use a reasonable timeout to still get the barrier provided by
ctrl-ping) |
bf23b9f86f6807c3029a6a46e1999ae0c87ca22a |
|
20-Apr-2015 |
Nir Soffer <nirsof@gmail.com> |
udev: settle should return immediately when timeout is 0
udevadm manual says:
A value of 0 will check if the queue is empty and always return
immediately.
However, currently we ignore the deadline if the value is 0, and wait
without any limit.
Zero timeout behaved according to the documentation until commit
ead7c62ab7 (udevadm: settle - kill alarm()). Looking at this patch, it
seems that the behavior change was unintended.
This patch restores the documented behavior. |
0736455b1186c9515e0f093e1e686e684d225787 |
|
11-Apr-2015 |
Nir Soffer <nirsof@gmail.com> |
udev: restore udevadm settle timeout
Commit 9ea28c55a2 (udev: remove seqnum API and all assumptions about
seqnums) introduced a regresion, ignoring the timeout option when
waiting until the event queue is empty.
Previously, if the udev event queue was not empty when the timeout was
expired, udevadm settle was returning with exit code 1. To check if the
queue is empty, you could invoke udevadm settle with timeout=0. This
patch restores the previous behavior.
(David: fixed timeout==0 handling and dropped redundant assignment) |
83be2c398589a3d64db5999cfd5527c5219bff46 |
|
20-May-2014 |
Harald Hoyer <harald@redhat.com> |
udevadm-settle: fixed return code for empty queue
If the udev queue is empty and "/run/udev/queue" does not exist,
"udevadm settle" would return with EXIT_FAILURE, because the inotify on
"/run/udev/queue" would fail with ENOENT.
This patch lets "udevadm settle" exit with EXIT_SUCCESS in this case. |