| Tweetie Pooh 2004-01-23, 4:33 pm |
| "LM" <lindamar02@yahoo.com> honoured comp.unix.admin on Fri 15 Aug 2003
03:22:05a with news:1060914125.391530@cswreg.cos.agilent.com:
quote:
> Can someone tell me what exactly happens to the machine when this
> happens? All that the admin of the existing NIS network tells me is that
> the passwd file will become remote (my experience with yppasswd is very
> very old..) and nothing else changes on the local machine. I don't
> really believe that, and I have a feeling that the sys admin is trying
> to pull a fast one on me since they are hungry for this high-end machine
> and I get the sense that they really don't care about the local users at
> all. I'm the only advocate... There's gotta be some other changes to
> the local machine that is more substantial than that when it is
> assimilated...
>
An NIS client can look at central files for admin/config.
In Solaris
/etc/nsswitch.conf
This tells where to look for a resourse. This can be central, local or both
and which first.
/etc/<others>
Add special entries to place the NIS stuff.
You can still add local users. One good idea is to reserve certain ID values
for local and the remainded for central. This prevents clashes.
You can also overwrite part of the central entry locally. ie tell the login
system to get users entry from the NIS server but local change the shell.
root often will remain local since you may need to log in at
maintenance/single user mode before networking is up. A local root will not
be able to change entries in the NIS database though unless set up to.
|