View Full Version : network startup problem

4th October 2009, 11:51 AM
I have a problem with atutofs/nis/dhcp

My workstation installed with FC11. It received IP from the server,
it then mounts the home directory from same server using autofs/nis,
the user logs in to X using nis based passwd file.

After reboot - X does not show the users.
Looking in messages, I think that the IP address is received too late - after
autofs/ypbind started. If I restart autofs, everything works fine at this time.

How can I make sure the init.d sequence does not proceed past network setup until
it completes?
How can I find out what's wrong with the dhcp getting its address?
Any other ideas?


14th October 2009, 03:20 PM
It looks like the problem is specific to intel e1000e based cards, that for some reason take a
very long time to negotiate speed with the switch. This causes the dhcp process to be delayed a lot, possible being left in the background while other services continue.

ypbind continues to bind to the server, but autofs, once it fails to load auto,master does not

A sort of proof I made for myself was to add a loop in autofs service which waits for yptest to succeed before it runs the automount process. This works, but it is not a solution.

Still looking for ideas.