Date: Thu, 21 May 1998 17:57:56 -0700 (PDT) From: Tom <tom@uniserve.com> To: Atipa <freebsd@atipa.com> Cc: jkh@time.cdrom.com, Barry Lustig <barry@lustig.com>, freebsd-stable@FreeBSD.ORG Subject: Re: YP Problems on 2.2.6 Stable Message-ID: <Pine.BSF.3.96.980521174905.11233A-100000@shell.uniserve.ca> In-Reply-To: <Pine.BSF.3.96.980521171143.3100A-100000@altrox.atipa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 May 1998, Atipa wrote: > > > I have problems too. I don't think their "fixes" improved stability as > > What fixes? Who is "their"? > > From 2.2.6 RELEASE NOTE: > o Various improvements to the NIS code. > > Does not say by whom. Man pages not updated since the 1995, so I don't > think "whom" would be listed there. I have searched through the mailing > list archives and not successfully found the maintainer(s) of NIS stuff. I don't think any improvements were made between 2.2.6 and 2.2.5. I was working with Bill Paul on a memory leak in the YP client lib, but I couldn't test his fix quickly enough... In case you didn't get that, Bill Paul is the maintainer, and his name is all over the stuff, and all over the mailing lists. > > > they should have. I have my NIS master on a different subnet, so I must > > > use "ypbind -s -ypsetme; ypset <nis_master_host>". I always get an error, > > > but the ypset works no problem! Freakin weird if you ask me. > > > What error? You can get timeout errors in that config before ypbind > > becomes bound, but that is normal. > > No, I means _error messages_. It says, "Sorry, can't ypbind for host foo > on domain bar." But it does! It does delay (like a timeout), and you would > think it didn't work, but it did. Definitely a misfeature. > > <foo>% domainname > bar > > <foo>% ypwich > (whatever you ypset to works) Never seen that. > > I use a special ypbind that can find non-local servers. > How? How can you tell it what broadcast addrs to look for if they are not > on your same wire? That would be a nifty addition to the package. You tell ypbind where the various possible YP servers are. See the manpage for current's ypbind. > > > I also think the docs are _really_ lacking. > > > > Docs are pretty good. I setup NIS for the first time from them two > > years ago. There are man pages for ypbind, ypserv, and the overall yp > > manpage. > > Well, they are admittedly bad. They themselves say to find a version of > Solaris and look at their man pages. I know Theo de Raadt has better > things to do w/ his time these days than support NIS on FreeBSD. Huh? Theo hasn't touched that code in a while. I also don't find any references to "Solaris" in those manpages, so I don't even know what you are looking at. > I have asked several questions about how to set up slave servers, and > noone can tell me. The man pages do not reference that at all. If I ever > find out, I will update the docs. Huh? I've never seen it. Slave servers are EASY. Just set the domainname, run ypserv, add the slave's name to ypservers on the master, enable map pushes in the Makefile, and rebuild all the maps. Basically, there are no specific instructions for a slave server, because you just need to read the ypserv, yp, and ypbind manpage, and put 2 and 2 together. I've got a master and a slave YP running in a hybrid mode (they are clients to themselves) plus one other pure YP client. > Kevin Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980521174905.11233A-100000>