On lundi, 6 novembre 2017 18.58:41 h CET Manfred Hollstein wrote:
On Mon, 06 Nov 2017, 18:34:12 +0100, Bruno Friedmann wrote:
On lundi, 6 novembre 2017 17.24:52 h CET Manfred Hollstein wrote:
[...]
Wutt not what I'm seeing on Leap 42.3 with both dual stack active and functionnal. I've all my network card setup as bootproto='static'
That's what I have here, too, but only for the network _cards_; the new computer I'm using has a wlan interface in addition, for which the BOOTPROTO is set to "dhcp4", but it is not automatically enabled, i.e. it is off.
But both wicked-dhcpv4 and v6 are enabled up and running.
Yeah, I just saw this:
# systemd-analyze blame | grep wicked 3.546s wicked.service 5ms wickedd-dhcp4.service 4ms wickedd-auto4.service 4ms wickedd-dhcp6.service 2ms wickedd.service 2ms wickedd-nanny.service
So, the dhcp services have been started, but as you can see, they don't have a _real_ effect on the boot time.
As it was an upgrade from 42.1, perhaps its a bug in term of migration. But editing the interface with yast doesn't change the status of wicked-dhcp
If someone else see the same, then it a bug to report.
I agree, if Carlos doesn't actually use the DHCP mode during boot, there shouldn't be a delay of 20 seconds; this smells like a bug.
Cheers.
l8er manfred
They have an impact here 8.119s wicked.service 38ms wickedd-auto4.service 36ms wickedd-dhcp4.service 35ms wickedd-dhcp6.service 7ms wickedd-nanny.service 5ms wickedd.service I've disabled them now, I will see next reboot how much it took. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org