On Mon, 2017-11-06 at 16:45 +0100, Carlos E. R. wrote:
On Monday, 2017-11-06 at 16:14 +0100, Dominique Leuenberger / DimStar wrote:
On Mon, 2017-11-06 at 16:07 +0100, Robert Kaiser wrote:
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.
this sounds a lot like https://bugzilla.opensuse.org/show_bug.cgi?id=779928
Maybe, I do not have IPv6, so an attempt to get an address via dhcp6 will fail.
Not having ipv6 is exactly the problem for that bug - it will wait like 20s to acknwoledge there is no reply Cheers Dominique