Very Computer

Anyway, I am leaving for another job and one of the last things I am considering doing
is transitioning the network to NIS from NIS+.  I still haven't made the decision, but
*if* I do, is there any reason I can't:

   - install NSKIT 1.2 on the server running 2.4
   - run NIS on all of the clients at the same time they are running NIS+
   - turn off NIS+ on the 2.3 server and all clients once NIS is working?

By turning off NIS+ I mean stopping the daemons on all machines, wiping out /var/nis/*,
taking stuff out of rc.stuff, etc.

After that, I would make the 2.3 server an NIS slave server (maybe after upgrading to
2.4, maybe not).  Thanks for any input/advice/criticism....

--
Wallace (Wally) Blackburn               .sig under construction

: I have a network consisting of 2 Sparc20 servers (one on 2.3 one on
: 2.4), 19 Sparc20 machines running a lab test tool, and 47 Sparc5s as
: user workstations.  I've been running NIS+ and had my share of pain
: with it.  When it works it is nice, but when it breaks it sucks.

: Anyway, I am leaving for another job and one of the last things I am
: considering doing is transitioning the network to NIS from NIS+.  I
: still haven't made the decision, but *if* I do, is there any reason I
: can't:

Umm, usually I look for easy busy work to fill out my time to the next
job.  But, if you really "love" (read, hate) your soon to be previous
employer...

If you don't want to stick with NIS+ (which is sad, because you are a
Sol2 site), you need to dump your tables.  Get the NSKIT and then
reload into NIS.  Then set nsswitch.conf to nis.

I would not recommend running NIS and NIS+ at the same time, if fact,
I don't think you can.  Although you can run NIS+ in compat mode, I
don't think it's what you're looking for.

With proper planning, the transition can be done in a few hours (most
likely two hours of down time).

: By turning off NIS+ I mean stopping the daemons on all machines,
: wiping out /var/nis/*, taking stuff out of rc.stuff, etc.

Proceedure:

* Install NSKIT
* Dump NIS+ tables
* kill rpc.nisd
* Nuke /var/nis
* Setup YP/NIS directories
* Startup yp.serv
* Push maps
* Reboot
* Reconfigure clients

Since I have never used NSKIT, I don't know what it does to
/etc/init.d/rpc, however you want to make sure that rpc.nisd doesn't
get run.

: After that, I would make the 2.3 server an NIS slave server (maybe
: after upgrading to 2.4, maybe not).  Thanks for any
: input/advice/criticism....

Go for it.

You are going to upgrade OS's before you leave?  You *must* really
"love" your soon to be former employers.

Good luck.  I still think NIS+ is the way to go with Sol2 machines.
It gets better with each passing moment.

cfs
--
/-------------------\  Charles "*-Buddha" Stephens
| HELLO, my name is |  UNIX Systems Administrator
|-------------------|  Network Systems/Open Systems Group,

| Charles Stephens  |  Emory University, Atlanta, Georgia, USA
|                   |  "You shall soon achieve perfection."  -Fortune Cookie
\-------------------/     http://www.veryComputer.com/~cfs