Ok...the other problem we are having is that all of our servers have
different directory structures...and each user may have a different
directory path on each server....how do we over come this? I'm looking
for something that will just check an authentication database for
username and password and/or that database will give the correct path
based on the server he/she is authenticating from. The reason I'm
looking for a solution is that the cobalts put their users in a wierd
directory structure as opposed to the linux standard of
/home/*accountname" or the sysv standard of /usr/"accountname"
Any clues?? Or have I confused you all??
----- Original Message -----
From: David L. Parsley (lkml account) <firstname.lastname@example.org>
To: Alan Cox <email@example.com>
Cc: Brent Clements <firstname.lastname@example.org>;
Sent: Friday, January 07, 2000 7:23 PM
Subject: Re: Best Network setup for linux/unix
> On Fri, 7 Jan 2000, Alan Cox wrote:
> > > I need some suggestions on setting up a unix server farm
that all =
> > > gets authenticated from a single server. What is the best way of
> > > this?
> > Advice #1: Don't do it. Not for servers. Otherwise the failure of
> > authentication host leaves you dead in the water.
> > > I know I could use NIS but is that really the best way to do it?
> > NIS works, its not terribly secure. LDAP is more powerful but a
> > to set up
> Yup, I think RedHat jumped the gun a tad with the phrase 'integrated
> - but I managed pam & nss ldap on the laptop (and now I'll implement
> the college). I agree a monolithic auth server is a single point of
> failure and bad. Is there a nice way to do failover w/ LDAP? (I
> remember anything from pam_ldap and nss_ldap) Heartbeating and such
> would make it a _real_ bugger to set up.
> > > problem we are having is that we are using two cobalts, one
intel web =
> > > server, and finally one intel mail server. I want a centralized
> > NIS works across OS's and across platforms. Well mostly anyway 8)
> > Alan
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> > the body of a message to email@example.com
> - --
> David L. Parsley
> Network Specialist
> City of Salem Schools
> To unsubscribe from this list: send the line "unsubscribe linux-net"
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to email@example.com
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:28 EST