That did it. I don't have an idea what nscd does, anyone care to explain
why caused that problem.

Chris


On Sun, 2003-03-16 at 14:59, nate wrote:
> Chris Mason said:
> > I admin several Redhat servers, and on one of them, after I ran up2date
> > and brought it up to date, my own username, masonc, could not login. When
> > I ssh to the box using public key authentication, I get:
> >
> > id: cannot find name for user ID 503
> > id: cannot find name for user ID 503
> > [I have no [EMAIL PROTECTED] ]$
> 
> I have seen this most often on systems that use libnss-ldap, where
> nscd was restarted incorrectly, and remained in a bad state(this may
> be true on NIS/NIS+ systems as well but haven't personally experienced
> it on such), restarting nscd always immediately solved the problem for
> me.
> 
> nate
> 
> 
> 
> 
> 
> -- 
> redhat-list mailing list
> unsubscribe mailto:[EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to