mkhaw@teknowledge-vaxc.ARPA (Mike Khaw) (12/08/87)
Several weeks ago I posted a request for help with an Ultrix 2.0 yp
problem: I was trying to set up a VAXstation as a yp client in an
existing yp domain consisting (until then) exclusively of Sun-3s.
Ypbind would run and continually spawn and kill 2 child processes
(i.e., there were always 3 ypbinds running, but the PIDs of 2 of them
kept changing). Ypwhich would say "Domain teksun not bound". Domainname
would return "teksun" on both the VAXstation and the Sun yp server.
Ypset would also fail with (I think) "Domain teksun not bound".
I'd given up (DEC support wasn't able to shed any light on this) until
today, when I was obliged to try to solve this again. I offer the following
information in the hopes that others may find it of use.
It turns out that if, right after starting ypbind, I do
/usr/etc/yp/ypset -d `domainname` $SERVER_IP_ADDR
where $SERVER_IP_ADDR is the internet host NUMBER of the Sun yp server,
it all works. Previously, I'd used
/usr/etc/yp/ypset $SERVER_NAME
where $SERVER_NAME was the hostname of the Sun yp server. Since the Sun
yp server is listed in the VAXstation's /etc/hosts file, I still consider
this a bug in ultrix 2.0 yp, but at least there's a workaround.
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303