Date: Thu, 11 Feb 1999 13:56:26 -0500 (EST) From: Mikhail Teterin <mi@misha.cisco.com> To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Cc: bugs@FreeBSD.ORG Subject: Re: bin/10031: ypxfr does not work with Solaris master server(s) Message-ID: <199902111857.NAA18336@misha.cisco.com> In-Reply-To: <199902111847.NAA23584@skynet.ctr.columbia.edu> from Bill Paul at "Feb 11, 1999 01:47:51 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Paul wrote: > > That's quite possible, actually. The reason I started to bother was > > because yp-related lookups are very slow and fail on occasion here. > > Oh no you don't. You have other problems, file a new PR. None of this > "while I've got your ear stuff." "No I don't" what? Please, speak slower, English is not my native language... > > Good question. I do not have a login account there... > > Arrrrghhh... Well find out. It will probably enlighten the both of us. Judging by the login prompt: they both are SunOS 5.6... > Grrr! Read the ypwhich man page ... Yeap, you are right, `ypwhich -m' says the nis2 is the master for all of the databases. > > Well, not that I do not believe you, but yppoll does not work: > > # yppoll passwd > > yppoll: no such map passwd. Reason: YP server error > > GRRRR!!! You did not follow my instructions! This is what I said: I did, I did, calm down. The response was the same, and I only quoted one. > If you don't believe me, run 'yppoll passwd.byname' from the FreeBSD [...] -------------------- > Are these the same thing? No! Go back and do it again! % yppoll passwd.byname yppoll: no such map passwd.byname. Reason: YP server error > > Any chance of getting the initial databases from one of the funcitonal > > slaves? > > The whole point of this excersize is that the slave servers obtain > map updates from the master. If the master is not running, or if the > maps are being built with the wrong master name in them, then the > master/slave update mechanism won't work. You're supposed to _fix_ > this, not invent new and exciting ways to ignore it! March immediately > over to your Solaris admin and either pump him for the appropriate > information of get him to fix nis2. I understand. However, the admin's response is "we do not support FreeBSD". -mi 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?199902111857.NAA18336>