[SOLVED] systemd-udev-settle.service 20 second delay at boot

[waferhead]

Reinstalled MGA3B1/ran updates, uninstalled grub 1&2 and reinstalled grub2, works properly now.

On boot, there is a ~20 second pause after mounting home.

Note: Cannot disable the service (same for the fedora* services) , it gets automagically turned back on.
The little machine has a ~screaming fast SLC SSD, and a slow ULV core2 duo CPU @1.2 GHz, which seem to offset each other to a great extent.
Also there is an amazingly annoying new "are you sure you want to quit? box trying to close drakconf, but I digress.

I'm getting the following from systemd-analyze:

Code: Select all

[root@x300 greg]# systemd-analyze blame
 20895ms systemd-udev-settle.service
  5565ms network-up.service
  5134ms shorewall.service
  2383ms network.service
  2356ms mandriva-everytime.service
   652ms resolvconf.service
   644ms partmon.service
   446ms microcode_ctl.service
   404ms upower.service
   350ms bluetooth.service
   323ms sensord.service
   285ms fedora-readonly.service
   277ms udisksd.service
   247ms lm_sensors.service
   219ms systemd-logind.service
   192ms iptables.service
   190ms systemd-readahead-collect.service
,,,etc,,,


[martinw]

Also there is an amazingly annoying new "are you sure you want to quit? box trying to close drakconf, but I digress.

See https://bugs.mageia.org/show_bug.cgi?id=8476. Maybe if enough people complain, it will be removed.

[wilcal]

Also there is an amazingly annoying new "are you sure you want to quit? box trying to close drakconf, but I digress.

That is a new "feature" that probably needs to be debated here.

[waferhead]

Also there is an amazingly annoying new "are you sure you want to quit? box trying to close drakconf, but I digress.

That is a new "feature" that probably needs to be debated here.

It probably deserves its own thread...

[isadora]

...............


It probably deserves its own thread...

Agree.

[waferhead]

The delay seems to have been fixed in course of normal updates, closing.