On 04/21/2018 02:18 AM, Felix Miata wrote:
Andrei Borzenkov composed on 2018-04-21 08:44 (UTC+0300):
David C. Rankin composed:
Felix Miata wrote:
Since for me this dates back to 13.2 and happens on both 15.0 and TW, I decided to go ahead and file a bug, even though only some installations have this problem: http://bugzilla.opensuse.org/show_bug.cgi?id=1090188
I added my information as well, thanks.
Yet another "bug report" that just wastes scarce time of developers.
This is normal behavior, wicked waits for link on device, if you do not like it - disable it. How to do it is described in (surprise) "man ifcfg".
If you look at note 1 in comment 0 of the bug you might notice among the 3 openSUSE installations on the same machine, two have the problem, the other does not. All three have the identical BOOTPROTO, STARTMODE and IPADDR lines that the YaST installer created and no other lines in /etc/sysconfig/network/ifcfg-<NIC>. All were installed within a matter of hours from each other using the same installation cmdline network specification (per LINUXRC). Why the difference in behavior among the three installations? Does Wicked assign a random value for LINK_REQUIRED in the bowels of /usr/ or elsewhere when YaST doesn't configure one in ifcfg-<NIC>?
LINK_REQUIRED='no' I found thanks to Andrei does keep wicked startup time the same with or without ethernet cable connected. :-)
Felix, THANK YOU!!! for pointing me in the right direction. The problem is the openSuSE config for wicked. Buried down in /etc/sysconfig/network/config is: WAIT_FOR_INTERFACES="30" which cannot be set via YAST/Nework (your adapter). 30 seconds twiddling thumbs is a ridiculous amount of time to wait for interfaces that come up instantaneously. Setting it to "5" is more than sufficient. Then next problem is the global default of auto for: ## Type: list(auto,yes,no) ## Default: "auto" # # Permits to specify/modify a global ifcfg default. Use with care! # # This settings breaks rules for many things, which require carrier # before they can start, e.g. L2 link protocols, link authentication, # ipv4 duplicate address detection, ipv6 duplicate detection will # happen "post-mortem" and maybe even cause to disable ipv6 at all. # See also "man ifcfg" for further informations. # LINK_REQUIRED="auto" (apparently "auto" means yes) This appears to be a holdover from the days you had to wait for a carrier before they can start. Thanks to Felix, I found this and set it to "no" on a per-interface basis in ifcfg-eth0, e.g. $ cat /etc/sysconfig/network/ifcfg-eth0 LINK_REQUIRED="no" BOOTPROTO='dhcp' STARTMODE='onboot' BROADCAST='' ETHTOOL_OPTIONS='' IFPLUGD_PRIORITY='0' IPADDR='' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' There is no way to set this through yast/network either. After making these changes, there is no 5 second delay at boot and the system comes right up: -- Logs begin at Mon 2018-04-02 18:49:33 CDT, end at Sat 2018-04-21 04:04:17 CDT. -- Apr 21 03:52:53 wizard systemd[1]: Starting wicked managed network interfaces... Apr 21 03:52:58 wizard wicked[1122]: lo setup-in-progress Apr 21 03:52:58 wizard wicked[1122]: wlan0 setup-in-progress Apr 21 03:52:58 wizard wicked[1122]: eth0 setup-in-progress Apr 21 03:52:58 wizard systemd[1]: Started wicked managed network interfaces. Creating and checking a plot of the startup: $ systemd-analyze plot > opensuse_boot.svg Shows I could reduce this further, as nothing is waiting on any of the devices, and SuSEFirewall comes right up (925ms) as soon as the 5 second delay times out. The 30 second delay is way way too long. Especially for my HP laptop that just sits there stalled until 1/2 minute rolls by until wicked times out and I can finish boot. After the changes, the entire boot, from Off/Cold to Kdm login takes less than the 30 seconds I would otherwise be waiting on wicked. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org