> Alex Bron wrote:
> Short: My NIS client kills the ypserv process at the server as soon as
> X is being used. What's happening?
The ypserv package shipped with Red Hat 6.1 was linked against NDBM,
which is _does not yet fully support_. It crashes in serveral routines
when trying to free memory that was not malloced. The release on the
errata site is linked agains GDBM, and does not have these problems.
Get it.
> Long: I have a RedHat server (RedHat 6.1), offering DNS, NIS, NFS and
> some other services. The server itself is also a NIS client.
Do NOT run ypbind on a machine that is also a ypserv'er. Programs that
use getpwent() to examine user records will get all records twice. If
these programs update the password file, then bad things result :)
> I can use
> this server just as I want to, allowing NIS users to log on to the box
> in both textmode and X graphical mode.
As expected, NIS isn't actually queried on that machine.
> Using run-level 3, I can login, but when I start X (startx)
> the ypserv process on the server gets killed and I get all kinds of
> mysterious RPC errors on my client.
Actually, the server died when you logged in. Try to 'ls -l' and you
will probably notice a long delay while NIS tryies to look up your
UID's. (Unless nscd has them chached...)
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
