topic Re: NIS ypbind question in Operating System - HP-UX

NIS ypbind question

Alex Lavrov. — Mon, 05 Sep 2005 08:18:39 GMT

Hello,

I set the slave server to bind with "-ypsetme" options. That means, that it should bind only to itself.

After I start nis client, I do:
ypwhich

And ofcourse I expect that it will bind to itself, but for some reason it's binds always to another slave and totaly ignores "-ypsetme" option.

I restarted it 20 times, nothing help.

Any ideas?

Thanx.

Re: NIS ypbind question

Alessandro Pilati — Mon, 05 Sep 2005 09:08:13 GMT

Alex,
try to follow this procedure:

1)Log in as root to the slave server.

2)In the /etc/rc.config.d/namesvrs file, add -ypset to the YPBIND_OPTIONS variable as follows:

YPBIND_OPTIONS="-ypsetme"

3)Issue the following commands to restart ypbind (the NIS client process) on the slave server:

/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start

4)Issue the following command to force the NIS client process on the slave server to bind to the server process on the same host:

/usr/sbin/ypset slave_server_name

5)Issue the following command to check whether the NIS slave server is working:

/usr/bin/ypwhich

The ypwhich command should return the host name of the slave server.

The ypsetme option allows you only to run ypset from the current host, but doesn't set itself the NIS server you want to connect to.
The server must specified with the ypset.

Regards,
Alex

Re: NIS ypbind question

Alex Lavrov. — Mon, 05 Sep 2005 11:05:36 GMT

OK, thanx, I'll try it tomorrow.

Alex.

Re: NIS ypbind question

Alex Lavrov. — Tue, 06 Sep 2005 04:39:19 GMT

Thanx, it seems that I didn't read the man explanation close enough.

Alex.