Bug 70827 – autofs init scripts need more info when failure occurs

• Product: Gentoo Linux
• Status: RESOLVED CANTFIX

[Description Quentin Arce 2004-11-11 11:04:45 UTC]

when autofs is started on my system the init scripts report no problems.  When I check autofs is not running.  An /etc/init.d/autofs reload tries to kill a number of pids that do not exist.  After looking at this problem for about 15 min I found that I had compiled autofs4 as a module and I had not insmoded it.  There should be some sort of check if autofs is supported by the kernel and they insmod the module if it is a module and not compiled in.

Reproducible: Always
Steps to Reproduce:
1.Build kernel with autofs4 as a module
2.Install autofs
3.start autofs
4.reload autofs
5.find real problem by checking /var/log/daemons.log



Expected Results:  
working autofs or at lease clear error that it did not start and that you 
should check the daemon.log file  

I think that covers it.  Give it a try

[Comment 1 Robin Johnson 2004-12-08 21:25:24 UTC]

unfortunetly that's really hard at autofs doesn't give any indication that an error has occured in any way that's quick to pick up.
it always exits with a 0 return value, even when there is stuff wrong, and never even sends output on stdout.

i'll put a chunk of code into the latest init script that check for the autofs module for you, and try to load it if needed, and fail otherwise.