🚀 go-pugleaf

In article <C0r2oG.43o@ddsw1.mcs.com> karl@ddsw1.mcs.com (Karl Denninger) writes:
>In article <1993Jan12.143608.5659@serveme.chi.il.us> greg@serveme.chi.il.us (Gregory Gulik) writes:
>>In article <MWS3SEHMH@linac.fnal.gov> matt@severian.chi.il.us (Matt Crawford) writes:
>>>
>>>This isn't a crash, per se.  Is it some known cause, like a full disk
>>>or like that-there?
>>
>>I think it had something to do with NIS getting messed up.
>>Go figure.
>
>Yeah, its known as "you're running a Sun -- so reboot the bastard"
>
>Suns are notorious, and have been for years, for getting their brains
>scrambled.  It is only recently that they've >begun< to clean up their act
>in the OS support area (ie: NIS, NFS, etc).  It still doesn't work quite
>right.
>
>BTW, what does CLOUT need NIS for if its one machine?
>
>--
>Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
>Data Line: [+1 312 248-0900]


Must be something in the way you have it configured.  We have not had
problems with ours since about the days od SunOS 3.0 5+years ago.  We
have over 100 machines serving a couple thousand accounts.  Granted NIS/YP
may be a problem if you deal with 6000+ accounts when it comes to updates,
etc, but for machines like clout and most others, I think you are barking
up the wrong tree.

--Gene