Bug 740983

Summary:	The autofs.service is started too early in
Product:	[Fedora] Fedora	Reporter:	David Highley <david.m.highley>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-25 10:01:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Highley 2011-09-24 03:26:32 UTC

Description of problem:
The autofs service seems to get started too early in the boot process.

Version-Release number of selected component (if applicable):
systemd-35-1.fc16.x86_64

How reproducible:
Every boot

Steps to Reproduce:
1.Boot and then try and login to an automounted home directory account.
2.
3.
  
Actual results:
Home directory not present.

Expected results:


Additional info:
systemctl restart autofs.service fixes the issue until another reboot. Was not able to fix the issue by putting the above command in the /etc/rc.d/rc.local file, did not know if that was still a work around with the demise of system V init processing.

Comment 1 David Highley 2011-09-24 03:32:29 UTC

I should have also mentioned that NIS is used to serve the auto.home information.

Comment 2 Michal Schmidt 2011-09-25 10:01:45 UTC


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