Ralf,
Check to see if your 11.x ypbind man page includes the info in the next paragraph In a nutshell, HP added the SUN ypbind /ypinit functionality to specify the NIS Servers in a "ypservers" file:
Client requests drive the binding process. As a request for an unbound domain comes in, the ypbind process broadcasts on the network, if the file /var/yp/binding/
/ypserversdoes not exist, trying to find a ypserv process serving maps within that NIS domain.
If the binding should be established by broadcasting, at least one ypserv process must exist on every network. If the file /var/yp/binding//ypservers is present, then ypbind will try to bind to one of the NIS servers in the order of its listing in the file. If ypbind was unable to bind to any one of the servers available in the list, it will try establishing a binding by broadcasting. The file, /var/yp/binding//ypservers, containing the list of NIS servers is created by invoking ypinit with -c option. (see ypinit(1M)).
** How to check to see if you have this functionality:
First, make certain your domainname has been specified. For example:
# domainname
test.com
Then,
As root, use the command:
/usr/newconfig/usr/sbin/ypinit -c
If you receive a usage error, you can't use the ypservers file and will need to continue to use YPSET as before.
OTHERWISE you will see this output:
# /usr/newconfig/usr/sbin/ypinit -c
If it is desired that NIS client, has to bind to a particular NIS server, a
list of NIS servers should be constructed. Please continue to add the names of
NIS servers in the order of preference, one per line. When done with the list,
type a or a return on a line by itself
next host to add:
...fill in the names of the servers.
You will need to do this on every NIS client. Or if all the NIS clients have the patched ypbind/ypinit, you can rcp/rdist the /var/yp/binding//ypservers to the other NIS clients.
ASIDE: I suggest using /usr/newconfig/usr/sbin/ypinit, since the ONC cumulative ("NFS") patch installs the updated ypinit script in /usr/newconfig/usr/sbin/ypinit only. This is because /usr/sbin/ypinit is often customized on NIS Servers, e.g. to add new maps or delete them. So, you will need to check /usr/newconfig/usr/sbin/ypinit against the version in /usr/sbin/ypinit and resolve any customizations on NIS Slave/masters if any. Save /usr/sbin/ypinit to /usr/sbin/ypinit.orig, then cp -p /usr/new/config/usr/sbin/ypinit /usr/sbin/ypinit, and edit the (now updated) /usr/sbin/ypinit.
Hope that helps,
-> Brian Hackley
Ask me about telecommuting!
