In article

<08054489-5b3c-424f­-ad62-fd08a82d6...@s­13g2000prd.googlegro­ups.com>,

prak <back_scrip...@yaho­o.com> wrote:

Don't use LINUX for any of the server functions. In many kernels, NFS

and NIS don't work except with other LINUX machines.

Have a master machine sitting in the datacenter that's backed up and

bottle fed regularly. Many site's I've been at also have DNS on this

machine, but YMMV.

Have at least 1 NIS slave machine on each network segment or use a

multi-homed system across a couple network segments. Some sites I've

been at have also used this as a file server.

Be careful of having lines in the groups map get to long. I think 1024

is the longest.

Think carefully about groups. If you're going to use NFS, the maximum

number of groups a user can be in is something like 16 or 32 (I forget,

I'll let you research that). If you need to use more than that you'll

have to use ACLs on machines that support that.

Use automounter for user and project directories. If files are stored

on servers that are backed up, you won't be backing up desktops. It

will save lots of network overhead.

Are you going to manage a hosts map or use DHCP? I don't know what that

entails but be sure the ranges are mapped in local DNS. Otherwise,

you'll have reverse lookup problems and slow remote logins.

--

DeeDee, don't press that button! DeeDee! NO! Dee...