Basil Chupin said the following on 09/20/2013 10:10 AM:
network.service took about 22 seconds to become active.
Yes I gathered that from what I saw when booting 13.1 Beta.
The question, of course, is what exactly, and why, should be taking so much time to activate the network. I am not using the new Network Manager (as far as I know) and there is nothing special about my setup - a wired modem/router with 2 computers on the LAN.
That question becomes 'what does it depend on?' It could also be 'what actually does 'network.service' mean? Does it just mean the Ethernet connection to the LAN? Or does it include the network SERVICES such as DNS/NAMED, any routing protocols and more? On my server DNS takes a long time to start because, as I've written before, I have the huge table from http://pgl.yoyo.org/as/serverlist.php?hostformat=bindconfig&showintro=1&mimetype=plaintext which takes a few tens of seconds to digest. Sensibly, DHCP depends on having DNS up so that it can tell the DNS server about hosts that now have an IP address that wasn't in the original. Until DHCP is up no other hosts on the LAN get an IP address :-( Until DNS is up the mail subsystem can't work. Until DNS is up SpamAssassin can't work so fetchmail can't work. And so it goes. So the question becomes 'what does it depend on?' What are your dependencies? Does the chart show them? -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org