Red Hat Bugzilla – Bug 476934
autofs starts before ypbind, so isn't using NIS-provided automount maps
Last modified: 2009-01-06 00:25:22 EST
Description of problem:
Both autofs and ypbind in rawhide (pre-F11) start with priority 28, but autofs is alphabetically before ypbind, so it starts before ypbind. This means autofs is not picking up any NIS-provided automount maps like it should.
Simply changing the priority in /etc/rc.d/init.d/autofs likely isn't the solution, as ypbind asks for a priority of 27, but is getting assigned a priority of 28 which then causes the conflict with autofs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install rawhide, requesting autofs and ypbind in your package list
see both start with S28, but autofs starts first.
autofs starts after ypbind finishes
Ian, is this a duplicate?
This is the second time we've seen this reported but we can't see
a problem with the init script indexes in current CVS. Please have
look though bug 475002 and add further findings to it.
*** This bug has been marked as a duplicate of bug 475002 ***