[systemd-devel] device units rely on udev rules?

Koen Kooi koen at dominion.thruhere.net
Tue May 10 04:47:21 PDT 2011


Op 10 mei 2011, om 12:28 heeft Kay Sievers het volgende geschreven:

> On Tue, May 10, 2011 at 12:22, Koen Kooi <koen at dominion.thruhere.net> wrote:
> 
>>>> It's 3 minutes exactly (+trigger and shell overhead) every time, so I guess I'm hitting some kind of timeout
>>> 
>>> It's 180 sec, yeah. Doesn't it print what device it waited for?
>> 
>> udevadm doesn't
>> 
>>> If you add: "... settle --timeout=10" does it print something?
>> 
>> root at beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle --timeout=10)
>> 
>> real    0m10.427s
>> user    0m0.023s
>> sys     0m0.102s
>> 
>> Changing it to '1' doesn't print anything either. Should udev-monitor print the device it's waiting for?
> 
> Hmm, settle should print it like (I added sleep 15 to /dev/null):
> 
>  time (udevadm trigger; udevadm settle --timeout=10)
> 
>  udevadm settle - timeout of 10 seconds reached, the event queue contains:
>    /sys/devices/virtual/mem/null (5709)
> 
>  real	0m10.131s
> 
> What udev version is that? I'm running current -git, maybe something
> was broken, don't know it though.

[  122.891967] <27>udevd[88]: unable to receive ctrl connection: Function not implemented

Time to rebuild eglibc I guess.


More information about the systemd-devel mailing list