[systemd-devel] udevadm settle takes too long to finish

[Robert Milasan]

On Sat, 7 Dec 2013 22:12:38 +0100
"Kay Sievers" <kay at vrfy.org> wrote:

> 
> Something on your system pulls it in, it should look like:
> # systemctl status systemd-udev-settle.service
> systemd-udev-settle.service - udev Wait for Complete Device
> Initialization Loaded: loaded
> (/usr/lib/systemd/system/systemd-udev-settle.service; static) Active:
> inactive (dead) Docs: man:udev(7)
>            man:systemd-udevd.service(8)
> 
> Maybe check in the output of:
>   systemd-analyze dump
> if it shows up somewhere, if you don't find it in the filesystem.
> 
> Kay
> 

From systemd-analyze dump:

        Wants: systemd-udevd.service
        WantedBy: lvm2-activation-early.service
        WantedBy: lvm2-activation.service
        Before: lvm2-activation-early.service
        Before: sysinit.target
        After: systemd-udev-trigger.service
        After: systemd-journald.socket
        References: systemd-udevd.service
        References: systemd-udev-trigger.service
        References: sysinit.target
        References: systemd-journald.socket
        ReferencedBy: lvm2-activation-early.service
        ReferencedBy: lvm2-activation.service

rmilasan at coolcat:~> systemctl status systemd-udev-settle.service 
systemd-udev-settle.service - udev Wait for Complete Device
Initialization Loaded: loaded
(/usr/lib/systemd/system/systemd-udev-settle.service; static) Active:
active (exited) since Sat 2013-12-07 21:48:22 CET; 40min ago Docs:
man:udev(7) man:systemd-udevd.service(8)
  Process: 349 ExecStart=/usr/bin/udevadm settle (code=exited,
status=0/SUCCESS) Main PID: 349 (code=exited, status=0/SUCCESS)


-- 
Robert Milasan

L3 Support Engineer
SUSE Linux (http://www.suse.com)
email: rmilasan at suse.com
GPG fingerprint: B6FE F4A8 0FA3 3040 3402  6FE7 2F64 167C 1909 6D1A