I'm back at the same trouble I had with RedHat 4.2 and ypbind. It seems
RedHat 5.2 is still short for [Not] Red[dy for NIS] Hat.
Issue one: As far as I can tell, there is a timing problem with the
placement of the rc3.d start script for ypbind. If I try to start ypbind
as per the default setup, I get a message
YPBINDPROC_DOMAIN: Domain not bound
and the system is flat out not bound to the domain. Stopping and
restarting ypbind resolves the problem. Moving ypbind to rc.local doesn't
help (i.e. I have the same problem). However, if I proceed the ypbind
command with, say, sleep 20, then I still get the YPBINDPROC_DOMAIN
message but the domain is bound. If I edit the original
/etc/rc.d/init.d/ypbind script and add a
sleep 30
before the daemon ypbind line all is well; i.e. ypbind is running as it
should when the system is fully booted. Sleep 10 doesn't get the job
done. This seems terribly bizarre to me, but those are the facts.
Issue two: The ypbind which ships with RedHat 5.2 seems to be unable to
deal with shadow NIS passwords. Even when running properly (i.e. I can
ypcat all the appropriate maps, in particular passwd.byname), I still
can't login using an NIS account.
Does anyone have any pearls of wisdom they can drop upon this lamentable
state of affairs?
**********************************************
The meek shall inherit nothing. - Frank Zappa
**********************************************
_ Patrick Goetz
_| ~-. Dept. of Mathematics
\, *_} The University of Texas at Austin [EMAIL PROTECTED]
\( Austin, Texas 78712-1084 Phone: (512) 232-2746
http://www.ma.utexas.edu/users/pgoetz
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
