Il 06/11/2017 16:07, Robert Kaiser ha scritto:
Carlos E. R. schrieb:
Look, on this desktop I have an SSD, and:
└─clamd.service @34.757s +11.407s └─network.target @34.733s └─wicked.service @14.681s +20.046s └─wickedd-nanny.service @14.648s +27ms └─wickedd.service @14.571s +20ms └─wickedd-dhcp4.service @14.498s +61ms └─SuSEfirewall2_init.service @14.171s +250ms └─basic.target @14.121s
See "wicked.service @14.681s +20.046s"? That's a huge time. Yet the firewall starts fast.
Ah, good to see that wicked is a problem for others as well. I guess it may wait for some device to start ups that isn't connected or for some DHCP6 or something else that is actually unneeded, I have a similar thing here. Would be interesting if that can be dealt with in some way as wicked needing more than half of the whole startup time isn't nice, esp. if it's waiting for stuff that's not really needed.
Yes wicked is a pain, like apparmor: Old system (core 2 duo with HDD): graphical.target @21.649s └─wicked.service @11.284s +7.797s └─wickedd-nanny.service @11.255s +27ms └─wickedd.service @11.138s +116ms └─wickedd-auto4.service @10.404s +732ms TW on a newer system (Athlon 860k with a slow HDD): graphical.target @57.559s └─wicked.service @29.161s +12.257s └─wickedd-nanny.service @28.703s +455ms └─wickedd.service @28.175s +526ms └─wickedd-auto4.service @25.805s +2.368s └─dbus.service @24.593s └─basic.target @24.591s └─paths.target @24.591s └─cups.path @24.591s └─sysinit.target @24.545s └─apparmor.service @1.827s +22.717s In both system ipv6 disable in Yast Bye, Daniele -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org