Bug 135900 - after boot, autofs must be restarted before it will mount /home/boston
Summary: after boot, autofs must be restarted before it will mount /home/boston
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Feist
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-15 18:21 UTC by Jay Fenlason
Modified: 2014-08-31 23:26 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2004-10-20 18:55:54 UTC


Attachments (Terms of Use)
/var/log/messages from fenlason-rhide (14 bytes, text/plain)
2004-10-18 21:40 UTC, Jay Fenlason
no flags Details

Description Jay Fenlason 2004-10-15 18:21:50 UTC
Description of problem: 
Autofs doesn't mount /home/boston until I do a "service autofs 
restart" after boot 
 
Version-Release number of selected component (if applicable): 
autofs-4.1.3-22 
 
How reproducible: 
Every time 
 
Steps to Reproduce: 
1.reboot fenlason-rhide 
2.log in as fenlason 
3.note that my home directory is not mounted 
   
Actual results: 
 
 
Expected results: 
 
 
Additional info:

Comment 1 Chris Feist 2004-10-18 21:08:56 UTC
Can you post all entries from your /var/log/messages file which
contain 'automount' or 'autofs'.

This could potentially be a problem w/ yp not coming up soon enough.

Comment 2 Jay Fenlason 2004-10-18 21:40:59 UTC
Created attachment 105402 [details]
/var/log/messages from fenlason-rhide

Comment 3 Chris Feist 2004-10-19 19:43:18 UTC
I was able to logon to fenlason-rhide, and for some reason autofs was
turned off:

[root@fenlason-rhide ~]# chkconfig --list autofs
autofs          0:off   1:off   2:off   3:off   4:off   5:off   6:off

After setting autofs to run in run levels 3-5 everything worked properly.

Investigation is underway to determine why autofs was turned off.

Comment 4 Chris Feist 2004-10-20 18:55:54 UTC
Unable to determine why autofs was turned off.  No apparent changes
have been made to the autofs rpm to cause this.  If the problem
re-occur's please re-open the bug.


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