"Joseph S. Gardner" wrote:
> Todd Swain wrote:
>
> > Joseph,
> > NFS and NIS are completely different. NFS is a type of file sharing and
> > NIS is a form of network based user management. They can be used in
> > conjunction with each other, or seperatley.
> >
> > --T.
> >
> >
> >
> > "Joseph S. Gardner" wrote:
>
> > > OK, the time has come to sit down and consolidate all my
> > > machines. I
> > > want to centralize my administration and user setup's, etc..
> > > is the
> > > "proper" method NSF or NIS or both/other??
> > >
> > > BTW what IS the difference anyway??
> > >
> > > Thanks,
> > > --
> > > Joseph S Gardner
>
> Hmm, based on this and further exploits of discovery then it seems that the
> "proper" method I would use is to setup NFS to allow file sharing and common
> directory paths (/home) and then run NIS on top of this to keep administration
> central. Is this correct??
>
> --
> Joseph S Gardner
>
> Senior Designer / Technical Support
> Kirby Co., Cleveland, OH
> [EMAIL PROTECTED]
>
> The box said,
> "Requires Windows 3.x or better",
> so I got Linux.
>
> Registered Linux user #1696600
NIS will keep passwords coordinated. To make "administration" central, you might
consider adding webmin on each user machine and having it listen oonly to the
administration IP. Then setting up cron jobs, executing custom commands, forcing
reboots on frozen keyboards (without having dirty buffers), etc. Can be done from
one location which does not need to be the server. (In fact, I recommend it is
the machine before the SysAdmin).
Civileme
Example: I use nfs to give users a common directory f\or exchanging files and to
download software, and I use nfs to give each user an individual backup area on
the main server. One of them used the backup area. Now every day, there are
cron jobs beginning mid-afternoon and running about 5 minutes apart to copy user
material on individual stations to their respective backup areas. I did this
without touching a single user machine other than my own.
