NIS, NIS-slave, Samba

Hi there,

We've built a Suse linux cluster using drbd, and now we want to make sure we
have a centralized passwd database using NIS.

Our configuration is as follows:
primary linux server, secondary linux server, samba, W2000 clients.
If the primary linux server fails, heartbeat makes sure the secondary linux
server takes over all relevant services, so users won't even notice.

What we don't have, is synchronization of /etc/passwd, /etc/group from
primary to secondary and v.v., so if a user is added, or a password is
changed,
the secondary server has to be updated manually for now...

Has anyone tried to setup NIS en NIS-slave to solve this?
What will happen when our primary server fails and a user wants to change
his password?


Thanks in advance,

Mark

I have NIS running between Solaris, HP-UX, Red Hat 8 and Mandrake 9.2, that
part of it works fine. The Solaris box is the NIS master, no slave servers
currently. My issue is in synchronization of the samba password file with
the Unix password file. My other issue, is to create an NIS map for the
smbpasswd file.

Dudley
"Mark - bvh" <(E-Mail Removed)> wrote in message
news:3ff54413$0$323$(E-Mail Removed)...
> Hi there,
>
> We've built a Suse linux cluster using drbd, and now we want to make sure
we
> have a centralized passwd database using NIS.
>
> Our configuration is as follows:
> primary linux server, secondary linux server, samba, W2000 clients.
> If the primary linux server fails, heartbeat makes sure the secondary
linux
> server takes over all relevant services, so users won't even notice.
>
> What we don't have, is synchronization of /etc/passwd, /etc/group from
> primary to secondary and v.v., so if a user is added, or a password is
> changed,
> the secondary server has to be updated manually for now...
>
> Has anyone tried to setup NIS en NIS-slave to solve this?
> What will happen when our primary server fails and a user wants to change
> his password?
>
>
> Thanks in advance,
>
> Mark
>
>