02.04.2016 17:35, Per Jessen пишет:
Per Jessen wrote:
leo.salm@gmx.at wrote:
Dave Howorth schrieb:
So since I've spent a lot of time watching Leap booting recently :( I noticed that there's a noticeable delay whilst it sits there waiting for wicked to do something*. I just had a look at a presentation about wicked and it appears to be designed to deal with network complexity, which I don't need. It also seems that Network Manager is the default for desktops, so I guess I selected something whilst installing.
Did you upgrade from 13.2 to Leap 42.1? I had the same delays on 2 of my machines after upgrading.
Having a look into /etc/sysconfig/network I found the file ifcfg-eno1 from 13.2. As this interface wasn't listed at the output of #> ip link I removed that file (after saving it to my home
Now i have: #> systemd-analyze blame 4.299s wicked.service
On my test desktop for Leap421, I see:
# systemd-analyze blame 20.261s wicked.service
FWIW, I added "--log-level debug" to wicked.service:
Apr 02 16:20:32 linux-imqk systemd[1]: Starting wicked managed network interfaces... Apr 02 16:20:32 linux-imqk wicked[932]: __ni_config_parse_ifconfig_source: Adding ifconfig firmware: Apr 02 16:20:32 linux-imqk wicked[932]: __ni_config_parse_ifconfig_source: Adding ifconfig compat: Apr 02 16:20:32 linux-imqk wicked[932]: __ni_config_parse_ifconfig_source: Adding ifconfig wicked: Apr 02 16:20:32 linux-imqk wicked[932]: trying to discover netif config via firmware service "ibft" Apr 02 16:20:32 linux-imqk wicked[932]: ni_netconfig_firmware_discovery: buffer has 0 bytes Apr 02 16:20:32 linux-imqk wicked[932]: ni_sysconfig_read(/etc/sysconfig/network/config) Apr 02 16:20:32 linux-imqk wicked[932]: ni_sysconfig_read(/etc/sysconfig/network/dhcp) Apr 02 16:20:32 linux-imqk wicked[932]: ni_suse_read_routes(/etc/sysconfig/network/routes) Apr 02 16:20:32 linux-imqk wicked[932]: Parsed route: ipv6 ::/0 via fe80::1 dev eth0 type unicast table main scope universe protocol boot Apr 02 16:20:32 linux-imqk wicked[932]: Reading sysctl file '/boot/sysctl.conf-4.1.15-8-default' Apr 02 16:20:32 linux-imqk wicked[932]: Reading sysctl file '/usr/lib/sysctl.d/50-default.conf' Apr 02 16:20:32 linux-imqk wicked[932]: Reading sysctl file '/etc/sysctl.conf' Apr 02 16:20:32 linux-imqk wicked[932]: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-eth0) Apr 02 16:20:32 linux-imqk wicked[932]: Assigned route to eth0: ipv6 ::/0 via fe80::1 dev eth0 type unicast table main scope universe protocol boot Apr 02 16:20:32 linux-imqk wicked[932]: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-lo) Apr 02 16:20:32 linux-imqk wicked[932]: ni_compat_generate_interfaces: compat:suse:/etc/sysconfig/network/ifcfg-eth0:0 Apr 02 16:20:32 linux-imqk wicked[932]: ni_compat_generate_interfaces: compat:suse:/etc/sysconfig/network/ifcfg-lo:0 Apr 02 16:20:32 linux-imqk wicked[932]: No valid configuration files found at /etc/wicked/ifconfig Apr 02 16:20:32 linux-imqk wicked[932]: lo: configuration applied to nanny Apr 02 16:20:32 linux-imqk wicked[932]: eth0: configuration applied to nanny Apr 02 16:20:55 office34 wicked[932]: lo up Apr 02 16:20:55 office34 wicked[932]: eth0 up Apr 02 16:20:55 office34 systemd[1]: Started wicked managed network interfaces.
Still 23 seconds unexplained after "eth0: configuration applied to nanny". It's not due to DHCP:
Try enabling debug on wickedd and wickedd-nanny services. The job of wicked.service is to only parse configuration and hand it off to wickedd. This is wickedd (and wickedd-nanny) job to actually do anything with it.
Apr 2 16:20:42 dresden dhcpd: DHCPREQUEST for 192.168.3.34 from 00:18:fe:6a:73:0b via eth0 Apr 2 16:20:42 dresden dhcpd: DHCPACK on 192.168.3.34 to 00:18:fe:6a:73:0b via eth0
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org