Re: udevadm settle timeout semantics

[Kay Sievers <kay.sievers-tD+1rO4QERM@public.gmane.org>]

On Thu, 2009-06-18 at 13:14 +0200, Seewer Philippe wrote:
> The manpage for udevadm (version 141) says about the timeout for settle 
> and --timeout:
> 
> [quote]
> udevadm settle [options]
>         Watches the udev event queue, and exits if all
>         current events are handled.
> 
> --timeout=seconds
>             Maximum number of seconds to wait for the event
>             queue to become empty. The default value is 180
>             seconds. A value of 0 will check if the queue
>             is empty and always return immediately.
> [/quote]
> 
> 
> Am I reading this correctly if I assume that udevadm has to wait for an 
> event to be "handled" regardless of the timeout value?
> 
> Example: dhclient has a default of 60 seconds to try to get an ip 
> address until it fails. udevadm settle waits for the whole 60 seconds to 
> pass regardless of the timeout parameter.
> 
> Is this behaviour as intended?

The timeout is the maximum to wait:

  $ echo 'RUN+="/bin/sleep 300"' > /etc/udev/rules.d/00.rules
  $ echo add > /sys/class/mem/zero/uevent

  $ time udevadm settle --timeout=3
  udevadm settle - timeout of 3 seconds reached, the event queue contains:
  /sys/devices/virtual/mem/zero (1796)

Not sure, udev 141 maybe had a bug here.

Thanks,
Kay

--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html