Arch Linux

ristretto

Member

Registered: 2007-07-06

Posts: 50

network daemon is slow to start and netfs fails, why?

DAEMONS=(syslog-ng network netfs crond sshd alsa)

If I have a network filesystem that needs the network (duh) to initialize
during netfs, it will fail.   Why?  Because network is taking a while
to actually create the network, and it is doing it asychronously.  What I mean is that
the network script completes and the boot process then continues to netfs, but
in actual fact, the network isn't up yet! 

If I put code in the network script to make it wait for a few seconds before completing,
in order to allow the actual network to come up, I can get the network to come up
and be ready before netfs runs.  And netfs then runs fine and starts it's file systems.

But, why is networking taking so long (like 6 seconds) to start, and why
doesn't it block during the init process, so dependancies will be assured
to have it when they run?

I'm somewhat new to ARCH.  Came from Gentoo, don't remember this being an
issue over there.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: network daemon is slow to start and netfs fails, why?

Are you on a wireless connection ? wireless often takes longer to initialize than wired.

If it's a wired connection with dhcp it could be due to a slow router.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

ristretto

Member

Registered: 2007-07-06

Posts: 50

Re: network daemon is slow to start and netfs fails, why?

It's wired, and static IP.

However, I forgot to mention that I'm bringing up a bridged interface.

BRIDGE_INTERFACES=(br0)
bridge_br0=(eth0)
br0="br0 192.168.0.40 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="eth0 0.0.0.0 promisc"
INTERFACES=(lo br0 eth0)

Perhaps herein is the problem.....

Last edited by ristretto (2007-07-24 20:19:02)