Bug 476934 - autofs starts before ypbind, so isn't using NIS-provided automount maps
Summary: autofs starts before ypbind, so isn't using NIS-provided automount maps
Keywords:
Status: CLOSED DUPLICATE of bug 475002
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ian Kent
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-18 02:45 UTC by Matt Domsch
Modified: 2009-01-06 05:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-01-06 05:25:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Domsch 2008-12-18 02:45:02 UTC
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):
autofs-5.0.4-4.x86_64
ypbind-1.20.4-11.fc11.x86_64
chkconfig-1.3.40-1.x86_64

How reproducible:
easy

Steps to Reproduce:
1. install rawhide, requesting autofs and ypbind in your package list
  
Actual results:
see both start with S28, but autofs starts first.


Expected results:
autofs starts after ypbind finishes

Comment 1 Jeff Moyer 2009-01-05 17:48:47 UTC
Ian, is this a duplicate?

Comment 2 Ian Kent 2009-01-06 05:24:51 UTC
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.

Comment 3 Ian Kent 2009-01-06 05:25:22 UTC

*** This bug has been marked as a duplicate of bug 475002 ***


Note You need to log in before you can comment on or make changes to this bug.