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,
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
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 PRO
On Thu, 2002-08-15 at 01:39, Nicholas Yau wrote:
>
> - i have a server 7.0 which running NIS master . the server which i
> called him titan
> - all user are only added in titan . means i wanted to let user to use
> single password to login in anywhere.
> - i have a client 7.3 workstation which w
Okay
- i have a server 7.0 which running NIS master . the server which i
called him titan
- all user are only added in titan . means i wanted to let user to use
single password to login in anywhere.
- i have a client 7.3 workstation which wanted to authenticate user
which is added from titan.
[