Date: Thu, 11 Feb 1999 10:53:23 -0500 (EST) From: Mikhail Teterin <mi@misha.cisco.com> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/10031: ypxfr does not work with Solaris master server(s) Message-ID: <199902111553.KAA17750@misha.cisco.com>
next in thread | raw e-mail | index | archive | help
>Number: 10031 >Category: bin >Synopsis: ypxfr does not work with Solaris master server(s) >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 11 08:00:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: Mikhail Teterin >Release: FreeBSD 3.0-RELEASE i386 >Organization: Virtual Estates, Inc. >Environment: The master server nis1, apparently, redirects requests to another (slave?) server nis2. Both of them run Solaris. >Description: Local, FreeBSD-3.0-RELEASE machine tries to ypxfr -p /var/yp -h nis1 -c -d mydomain I put debug messages into ypxfr, which is why it is a bit more verbose here: ypxfr: couldn't create udp handle to ypserv: RPC: Program not registered ypxfr: source was: nis2 <-- my message on ypxfr_misc.c:229 ypxfr: failed to get order number of passwd.byname from nis2: RPC failure talking to server <-- my modifiction of message on ypxfr_main.c:368 >How-To-Repeat: See the setup above >Fix: I think, this has to do with ypxfr not failing over properly to the SunOS compatable strategy, but I'm not sure... I wish, there was a switch to not even try the FreeBSD-specific algorithm... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902111553.KAA17750>