Here I am reporting a compatibility problem between the newly introduced
in SL6 NetworkManager and the traditional ypbind and automount programs.

In the nutshell, after a reboot, automount does not "see" any mount points
defined in the NIS auto.master map file.

The boot sequence I am observing goes like this:
1) network manager runs, does it's stuff
2) ypbind starts, init script falsely reports successful start (ypwhich reports "not bound" but
this is redirected into /dev/null)
3) automount starts (and only if one enables automount logging in /etc/sysconfig/autofs,
would one see that it reports failure to access auto.master NIS map)
4) some time later, network manager finally starts the network interface
5) NIS ypbind becomes happy
6) but too late for automount, it does not know to reload auto.master

There are other problems with the NetworkManager, so simplest solution
is to "chkconfig NetworkManager off; service NetworkManager stop".

But now you have to manually edit the /etc/sysconfig/network-scripts/ifcfg-eth* files
because the usual system-config-network GUI was removed without replacement.

(This is in addition to the install-time incompatibility between the linux firewall
and NIS - if during install you enable both the firewall and NIS, on the next reboot
you get to wait for the infinite NIS timeout - because default firewall config
blocks NIS and NIS startup scripts do not know how to make a hole for themselves).


-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada