brad, the important thing was to keep ypserv from starting. if you had, say,
kill -9'ed ypserv everytime you booted your computer, the problem would've
gone away too. keeping the service from starting in the first place is not
a better fix; it's just more convenient. ;-P
did you upgrade redhat? i can imagine an upgrade procedure not respecting
the configuration an admin wants for his system.
pete
begin: Brad Benedict <[EMAIL PROTECTED]> quote
> Well, I am using Mandrake, which is Redhat for the most part. I didn't
> have to actually mess with those files though, I just went to the
> services somewhere in Mandrake Control Center and told them not start at
> boot time. Now I'm not having that problem. I don't know how it got
> started, though. Weird. Thanks for your help.
>
> Peter Jay Salzman wrote:
> >
> > i think more importantly than a copy of nsswitch is to simply not start the
> > service upon startup.
> >
> > you probably use redhat; i think the startup scripts are /etc/rc.d/rc3.d for
> > non-graphical startup of /etc/rc.d/rc5.d for graphical startup (it has been a
> > long time since i used redhat). for suse, it's rc2.d and rc5.d.
> >
> > one of your scripts starts ypserv, the server for NIS. it's probably called
> > something like S[0-9][0-9]ypserv or S[0-9][0-9]nis. first kill the service
> > by
> >
> > ./S[0-9][0-9]ypserv stop (for example)
> >
> > next, disable the service by moving
> >
> > S[0-9][0-9]ypserv to s[0-9][0-9]ypserv
> > S[0-9][0-9]nis to s[0-9][0-9]nis
> >
> > change the starting S to a small s. they won't be run on startup if they
> > begin with small s.
> >
> > while you're at it, no doubt you're running portmap. move the portmap
> > startup script to a small s as well.
> >
> > pete
--
"The following addresses had permanent fatal errors..." [EMAIL PROTECTED]
-- Mailer Daemon www.dirac.org/p
