On 16Jul2007 19:06, Andrew Robinson <awrobinson-ml@xxxxxxxxx> wrote: > I'm running FC6 on an eMachines laptop. I'm trying to configure NIS for my > growing home network. I seem to be having peculiar problems with the ypbind > init script. When I try to start the init script, it fails: > > [root@proteus ~]# /etc/rc.d/init.d/ypbind start > Starting NIS service: [ OK ] > Binding NIS service: ......... [FAILED] > Shutting down NIS service: [ OK ] > > However, I find that if I run the init script with the restart option, it > will often, but not always, succeed: > > [root@proteus run]# /etc/rc.d/init.d/ypbind restart > Shutting down NIS service: [FAILED] > Starting NIS service: [ OK ] > Binding NIS service: ... [ OK ] > > If I start ypbind by itself from a command line, it always succeeds. I > verify the successes and failures with ps, ypwhich and ypcat commands. > > Anyone have a clue as to what is going on here? I've been looking for some > indication in some log, but haven't found any. The goal is to get the init > script to succeed on boot up. (The init script gives the same messages at > bootup as it does when run with "start" from the command > line.) Try running it with "sh -x": sh -x /etc/init.d/ypbind start There's a loop just after the ypbind daemon is dispatched where it waits for ypbind to show in rpcinfo output. I've had that fail because the loop condition was testing for something that didn't happen. Anyway, you'll be able to see it trying rpcinfo and ypwhich in the loop. Really they should only be testing ypwhich, but you will soon know what's not working on your system. Cheers, -- Cameron Simpson <cs@xxxxxxxxxx> DoD#743 http://www.cskk.ezoshosting.com/cs/ Ninety percent of everything is crud. - Theodore Sturgeon
