On Wed, May 10, 2006 at 09:10, Troy Dawson wrote:
> Pann McCuaig wrote:
> >Symptoms are that ypserv is useful for a _very_ short time after
> >starting. I found that if I restarted ypserv and then ypbind on the NIS
> >server I had time to type 'ypcat hosts' twice and get results before the
> >following try hung.
> >
> >This is also the case for RHEL4 U3 (of course); I found the (short term)
> >fix on the web. Downgrade ypserv-2.13-9.x86_64 to ypserv-2.13-5.x86_64.
> >Works for me.
> >
> >Cheers,
> > Pann

> Hi Pann,
> Thanks for letting us know.  Where does it talk about this on the web. 

Troy,

I can't seem to find the page that told me a downgrade would fix the
issue (it did), but here are related links:

http://forum.nedlinux.nl/viewtopic.php?t=19621&postdays=0&postorder=asc&start=180&sid=5aa2299e06672754a7e1f0bf624cd7f0

http://bugs.centos.org/view.php?id=1253

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184405

> I'm curious if this is a x86_64 problem, or for all architectures.  Also 
> if this is a 'upgrade' problem, or if you have the same problem if you 
> do a fresh install.

I only have SL running on x86_64 machines and only one NIS server
running so I can't answer either question. Sorry.

Cheers,
 Pann
-- 
Pann McCuaig <[log in to unmask]>                212-854-8689
Systems Coordinator, Economics Department, Columbia University
Department Computing Resources:
               http://www.columbia.edu/cu/economics/computing/