Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jun 1997 15:00:02 -0700 (PDT)
From:      "Jin Guojun[ITG]" <jin@george.lbl.gov>
To:        freebsd-bugs
Subject:   Re: bin/3778: ypbind -S domainname,server1,... does not function
Message-ID:  <199706042200.PAA15568@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/3778; it has been noted by GNATS.

From: "Jin Guojun[ITG]" <jin@george.lbl.gov>
To: jin@iss-p1.lbl.gov, wpaul@skynet.ctr.columbia.edu
Cc: gnats@freebsd.org
Subject: Re: bin/3778: ypbind -S domainname,server1,... does not function
Date: Wed, 4 Jun 1997 14:47:08 -0700

 } > iss-p1# ypbind -S itg,george
 } > iss-p1# ypwhich   
 } > can't yp_bind: Reason: Domain not bound
 } > iss-p1# ps uxgw | grep yp
 } > root       190  0.0  0.9   192  276  ??  Ss   11:03AM    0:00.01 ypbind -S itg
 } > root       191  0.0  0.7   192  196  ??  S    11:03AM    0:00.00 ypbind -S itg
 } > iss-p1# which ypbind
 } > /usr/sbin/ypbind
 } > 
 } > Actually, the need is to specify mulltiple ypserver:
 } > 
 } > iss-p1# ypbind -S itg,george,slave1,slave2
 } > 
 } > for YP clients on different subnet.
 } 
 } Your description of the problem is not very clear: it is difficult to
 } tell exactly what it is you are trying to do.
 } 
 } My main question has to do with the client iss-p1 and the server george:
 } are they on the same subnet or not? If not, then the behavior you are
 } experiencing is not a bug: the -S flag does not provide any special
 } magic that allows NIS clients to bind to servers on remote subnets.
 
 I think the problem is clear. Otherwise, the man page is WRONG.
 According to the manual page -- ypbind -- the -S option is the better way
 for options -ypset and -ypsetme. Where is -ypset option used? at remote
 subnets. However, ypset can set only one ypserver for clients, and one ypserver
 always causes problem at remote site. Any router problem, ypserver problem,
 and network problem will kill all computers on a remote site.
 
 } With the -S flag, ypbind still transmits broadcasts and waits for replies
 } from qualified servers; the difference is that with the -S option, ypbind
 } will only honor replies from machines specified in the 'restricted mode'
 } server list. It will also only bind to the restricted mode domain.
 } 
 } The only way to ypbind do what you want it to do is to download the
 } ypbind source code from FreeBSD-current and compile that on your 2.2
 } system. (It should compile without any problem.) Once you have that,
 } use the following:
 } 
 } # ypbind -m -S domain,server1,server2,server3,server4,...
 } 
 } The -m flag is new: it tells ypbind to use a 'many-cast' instead of
 } a broadcast. This will allow it to bind to any of the servers even
 } if they are on remote subnets.
 
 I will try it and let you know the result.
 
 Thanks,
 
 -Jin
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706042200.PAA15568>