> Next problem: The net nis master runs slink. A slink client works after
> shadow has been configured and + added to /etc/shadow.
> A client runs partly potato, and does not work, i.e. it won't accept nis
> passwords. NIS itself appears to work, i.e. I can see the right owners of
> directo
Nils Rennebarth wrote:
> On Thu, Apr 22, 1999 at 10:01:53AM -0500, Jens B. Jorgensen wrote:
> > Hmmm, perhaps you'll have to generate your own intermediate passwd file to
> > generate the NIS maps. However, I would perhaps reconsider using shadow.
> > Unless
> > you're only serving up some (not r
In article <[EMAIL PROTECTED]>,
Jens B. Jorgensen <[EMAIL PROTECTED]> wrote:
>Hmmm, perhaps you'll have to generate your own intermediate passwd file to
>generate the NIS maps.
Ah yes, a possibility is to include the password in /etc/password, and
then filter that out again for shadow-capable host
Hmmm, perhaps you'll have to generate your own intermediate passwd file to
generate the NIS maps. However, I would perhaps reconsider using shadow. Unless
you're only serving up some (not root, etc.) passwords from NIS and have set up
NIS to work this way there's no benefit to running shadow locall
Again following up on my own posts, sigh:
On Thu, Apr 22, 1999 at 03:22:58PM +0200, Nils Rennebarth wrote:
> Next problem: The net nis master runs slink. A slink client works after
> shadow has been configured and + added to /etc/shadow.
> A client runs partly potato, and does not work, i.
I recently switched our nis master server from AIX to linux.
There are still a number of AIX hosts that should be run as nis clients or
nis slaves.
How do non shadow password clients get the password entries?
How do I make it on AIX which doesn't have shadow passwords but a
similar mechanism usin
6 matches
Mail list logo
