Date: Sun, 21 Feb 1999 18:47:47 -0600 (CST) From: John Kenagy <jktheowl@bga.com> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: cjclark@home.com, questions@FreeBSD.ORG, jktheowl@bga.com Subject: Re: NIS Message-ID: <199902220047.SAA07717@bga.com> In-Reply-To: <XFMail.990221204821.asmodai@wxs.nl> References: <199902211926.OAA17299@cc942873-a.ewndsr1.nj.home.com> <XFMail.990221204821.asmodai@wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeroen Ruigrok/Asmodai writes: > On 21-Feb-99 Crist J. Clark wrote: > > Jeroen Ruigrok/Asmodai wrote, > >> > >> On 21-Feb-99 Crist J. Clark wrote: > >> > Jeroen Ruigrok/Asmodai wrote, > >> >> On 20-Feb-99 Crist J. Clark wrote: > > > >> > This is good. Do you get any info? Perhaps I should have asked > >> > initially, why do you think that yppasswdd is hanging in the > >> > first place? > >> > >> OK, ye know the boot process of starting daemons? rpc.yppasswdd takes > >> far too long to my taste, I mean 5-10 minutes? I have to CTRL-C it to > >> continue booting. > > > > You've been rebooting everytime? Yee-uck. Once you kill the attempt to > > start rpc.yppasswdd, does the booting complete normally? Is ypserv up > > and running? > > I had to test a few rc scripts nonetheless as well as my new kernel, so it > was quite justified ;) > > > If you want to try to get rpc.yppasswdd running, you can just type > > 'rpc.yppasswdd <flags>' at the command line as root. No need to reboot > > everytime. > > I know, I tried that and it appeared to work ok, but when trying to ypbind > it appeared _not_ to work. That was before I added the server to ypservers > > I just tried it with localhost in ypservers, made the maps, and it still > hangs at boot up but it does work on the command line now though. > > >> >> ypservers is empty since there's only one server, > >> > > >> > Does the master need to have itself listed in ypservers? > >> > >> As far as I know/knew not. But as the follow-up mail from John points > >> out: it might be needed. Then remains the question how to put it in > >> there. As a hostname, a full host+domain name, an IP numeric? > > > > I think any of these would work. > > I tried it with localhost now. Sorry I'm slow getting back. I use the hostname in ypservers. "barnowl" and nothing else since it is the only server. > > I've been looking at the rpc.yppasswdd sources > > (/usr/src/usr.sbin/rpc.yppasswddd) and might have some guesses as to > > where it is hanging up. > > > > It might hang when looking for the master server in the > > 'ypxfr_get_master()' call (note that this function is in > > /usr/src/libexec/ypxfr/ypxfr_misc.c... you know how long it took to > > find that? :). I wonder if that is the problem since ypservers is > > empty and it is not looking in the right place. > > Well it shouldn't hang on that one now for the master not being present in > the ypservers file. It might however expect that the pushing of the maps to > slave servers be present. > > /var/yp/Makefile has NOPUSH= "True" in the file. > > > The problem I am having is that it is not too clear how NIS identifies > > which server is the master server. You are only supposed to run the > > Makefile on the master, but there is nothing I have found in it's > > comments or code that clearly states how the servers tell each other > > apart. Nor have I seen this in the documentation or source code. It > > makes me wonder if rpc.yppasswdd is not confused to and is looking for > > a master server that it cannot find, thus causing hangs. > > That's what I am looking at. It might need ypxfrd along with it, but that > wouldn't make sense in a single server setup. > rpc.ypxfrd _is_ running on my server. I do not recall specifically going about setting _that_ up when I started to do this, though. A HA! A quick check of /etc/rc shows it starting there if it's flag is not "NO". Now going back to the system configuration file shows _no_ entry for ypxfrd so it will never be "NO". I'm not sure if I deleted that line or what.;-) I noticed that you were not running the server as a client to itself. I do that as well. I do not really understand all of the ins and outs for that but Hal Stern's book seems to say that it is desireable so as to handle possible mail problems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902220047.SAA07717>