NIS logging

[Edwin R. Rivera]

hi again,

thanks for all of your help and support so far. I've managed to get my hp boxes running as both NIS master and NIS client server. I've also been able to successfully bind AIX and DEC clients to the server.

Now, I'm trying to configure my two sun boxes as clients. I've created my /etc/ethers, /etc/bootparams, and /etc/netmasks files, modified the $MASTER_MAPS variable in ypinit, and copied over the sun makefile from /var/yp.

i can't seem to:

1) run ypinit -m successfully from the NIS master server (hpux 10.2)

2) verify that the ethers and bootparams maps are being beilt in the /var/yp/mydomain directory.

does NIS log to syslogd ? i don't see any errors other than just make errors for a program called "multi" which i do see in my solaris box under /lib/netsvc/yp/ but i don't have that binary in the hp box.

thanks again,

edwin

[Shannon Petry]

I am not really sure what you are doing????

If your HP's are slave and master, why are you trying to run ypinit -m anywhere????/
ypinit -c #initialize yp client
ypinit -m #initialize yp master
ypinit -s #initialize yp slave

Most OS's support all 3 commands, but do not modify boot params to start YP! SunOS does, but Irix, HP-UX, and AIX require modifications.
HP-UX use SAM to configure client.
AIX use smit/smitty to configure client
Irix Modify boot scripts(if /etc/rc.config.d/nis.client contains on it may startup, however I have had to edit the startup script to bind to specific servers)
SunOS should not have to be modified. Once running ypinit -c, a directory called /var/yp will exist. As long as you specified the correct information prompted by ypinit -c you should be all set.

You should not have to copy makefiles, Makefile, ypmake, or any other files over! The only thing you may need to modify on the client is /etc/auto_master (if your using automounter maps) and any custom maps for automounting.

Depending on your version of Solaris, you may need to modify the search order for groups and passwords in /etc/nsswitch.conf. That is it!

I think this covers most of the basics. NIS is pretty straightforward on ALL Unices. Dont make more of it than you need to !

regards,
Shannon

[Edwin R. Rivera]

thanks shannon,

let me clear it up a little i guess.

1) sorry, i did mean ypinit -c on the sun clients.

2) as per the NIS configuration guide, the HP documentation says to (in order to bind Sun systems):
2a. - copy the sun /var/yp/Makefile
2b. - copy sun's bootparams, ethers, and netmasks files (i imagine to build those maps)
2c. - edit ypinit script to include those maps
2d. - re-run ypinit -m on the master to compile the additional maps.


i've tried just binding the sun clients to the hp, but it doesn't seem to work. i was curious about the logging so i can try and debug it a bit. i know the server (hp) is set up properly because my AIX and DEC boxes bind to it with no problems and i can log in and out of those clients as all different NIS users.

is there any other way i can see (from the hp) what the sun boxes are doing wrong?

thanks.

p.s. ypwhich returns the correct server on the sun boxes and ypbind starts up w/out any errors. ?? i'm confused!

-edwin