> 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 protocol. Unfortunately, no deal :-( I have around 20 boxes here. All of them were built as images from a reference machine, which received a clean squeeze install. For each machine, the image was dumped (with partimage), the hostname was changed, and the file /etc/udev/rules.d/70-persistent-net.rules was removed. So, all of them should behave the same way. However, some of them boot ok most of the times, others present NIS serve bind timeout everytime. Quite confusing... > In either case, I use the following configuration line for hosts in > /etc/nsswitch.conf. Tried that also. No improvement. In fact, I started getting some DNS trouble with a few older hosts. Looks like our DNS infrastructure is completely messed up Now, what really puzzles me: as I told before, "Restarting nis and autofs, in this order *does* solve the issue", and that's quite fast! Why doesn't it work at boot time? > I...sounds like > some incorrectly specified dependency in the /etc/init.d/* scripts. I agree with you, but I took a look at the scripts, and they look fine - autofs seems to depend on nis (I'm afraid I don't know this new init scheme very well, however). Anyway, this kind of issue would probably break things for a lot of people... > But because it is so annoying before too long someone > will have debugged it and gotten the offenders removed from the > mailing list. Got a probe email a few days ago - someone worked on it. Hope the issue is already solved. Best regards, João -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKaijp3KeG4vT9UtGzwaco9ivmVB+wq=skixmn2m3nbc6qh...@mail.gmail.com
