Never mind :)
I figured out that ypbind was set to use broadcast to resolve NIS
servers. I've added explicit server entries to /etc/yp.conf for
internal NIS servers at work. Now when ypbind starts, it tries each
server listed in turn, and simply FAILs when it can't find any of
them.
RTFM works! Whodathunkit? :)
-Sultan.
On 6/11/07, Sultan Saini <javagrendel@xxxxxxxxx> wrote:
Hi fed-heads,
I have a laptop that I use at work and at home. There is an NIS server
at work and the ypbind service automatically binds the NIS server at
boot.
The problem is that there is no NIS server at home, and during boot
NIS binding takes almost 5 minutes to fail before the rest of the boot
sequence proceeds. As you can imagine, this is a real pain in the
rear.
Here is the boot line from grub.conf:
title Fedora Core (2.6.22-rc3)
root (hd0,4)
kernel /vmlinuz-2.6.22-rc3 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.22-rc3.img
Ideally, I'd like ypbind to not take so long to fail binding, so that
I can use the same boot configuration at home and at work. Failing
that, is there a boot config that disable starting ypbind altogether?
That way I can use a different boot sequence at work and at home.
I'm running FC6 (with kernel 2.6.22rc3 prepatch) on a core 2 duo laptop.
Thanks in advance!
--
cheers....
....sultan
--
cheers....
....sultan
