>
>
> Sorry but I came late to this discussion. If you are still open to
> experimenting then I have another one for you. In the
> /etc/network/interfaces file do you have the interface listed? Or is
> it left to NetworkManager? If it is listed is it listed as
> "allow-hotplug eth0"?
Yes, lis
Joao Roscoe wrote:
> > Using it with NIS/YP is not so common so I think it
> > not unlikely that there is a bug related to it there.
> ...
> > Try this experiment. At the last point in the /etc/init.d/nis startup
> > script add a short sleep. That will give the daemons time to finish
> > and get
> If the hardware isn't completely identical then it is reasonable to
> have differences in the parallel boot timings.
Theoretically, the machines were identical, but I haven't inspected them to
make sure. The fact was: timing to suceed binding to NIS server was quite
different from one machine t
Joao Roscoe wrote:
> > Seems reasonable. I still use the broadcast protocol instead. But
> > what you are doing is supposed to work okay and I can only assume that
> > it does.
>
> Tried the broadcast protocol. Unfortunately, no deal :-(
Don't know. Works for me. I like it since that way any
> There was quite a long delay in that message! But what is a year
> among friends? :-)
Thanks for your patience :-)
> Seems reasonable. I still use the broadcast protocol instead. But
> what you are doing is supposed to work okay and I can only assume that
> it does.
Tried the broadcast pro
Joao Roscoe wrote:
> Ok, I really mixed things up. I'm sorry (and I'm also very sorry for
> the *huge* delay in answering to this thread).
There was quite a long delay in that message! But what is a year
among friends? :-)
> I meant that **ypbind** fails to bind to ypserver.
A critical differe
Ok, I really mixed things up. I'm sorry (and I'm also very sorry for
the *huge* delay in answering to this thread).
I meant that **ypbind** fails to bind to ypserver.
And yes, the NIS domain servers are specified in yp.conf by their
fully qualified names, and those names are hardcoded in /etc/host
Ok, I really mixed things up. I'm sorry (and I'm also very sorry for
the *huge* delayu answering to this thread).
I meant that **ypbind** fails to bind to ypserver.
And yes, the NIS domain servers are specified in yp.conf by their
fully qualified names, and those names are hardcoded in /etc/hosts
Joao Roscoe wrote:
> I have a bunch of squeeze boxes running with nis and autofs. All are working
> well, no performance issues. However, at boot time, sporadically, bind times
> out, and the machine goes up without nis.
Your words say "bind times out" and "nis" fails but what does bind
have to do
9 matches
Mail list logo
