I discovered the reason why nis wasn't starting. I had the name of the server
instead of the IP address (sorry, I overlooked the instructions about the IP
address in yp.conf).
Now ypbind always starts. And autofs seems to read auto.master from the NIS
server properly. I have rebooted about
** Changed in: autofs5 (Ubuntu)
Importance: Medium = Wishlist
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = Opinion
--
initialization of autofs is erratic (no nis maps available)
https://bugs.launchpad.net/bugs/619947
You received this bug notification because you are a member
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/619947/+attachment/1498044/+files/Dependencies.txt
--
initialization of autofs is erratic (no nis maps available)
https://bugs.launchpad.net/bugs/619947
You received this bug notification because you are a member of
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Please clarify - are you saying that upon rebooting the system, you
randomly get either statd or nis not starting? While other times both start
fine and then autofs starts fine? If so, do you have any idea why nis
