SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hmm. For some reason or another, the autofs maintainers removed the status command from rc.autofs between 4.1.4 and 5.0.5. Too bad they didn't bother to update the man page.
So, I would go edit /etc/default/autofs by uncommenting the line containing OPTIONS="" (it's almost at the end of the file) and setting the options to "-d"...
Code:
OPTIONS="-d"
...like so to turn on verbose debugging.
I'd then issue an
Code:
/etc/rc.d/rc.autofs restart
command, attempt to access one of those mount points and see what shows up in /var/log/messages and /var/log/syslog.
Hmm. For some reason or another, the autofs maintainers removed the status command from rc.autofs between 4.1.4 and 5.0.5. Too bad they didn't bother to update the man page.
So, I would go edit /etc/default/autofs by uncommenting the line containing OPTIONS="" (it's almost at the end of the file) and setting the options to "-d"...
Code:
OPTIONS="-d"
...like so to turn on verbose debugging.
I'd then issue an
Code:
/etc/rc.d/rc.autofs restart
command, attempt to access one of those mount points and see what shows up in /var/log/messages and /var/log/syslog.
Excellent.. Thank you. Turning on debugging helped me comb the logs.. finally got this working!
Excellent.. Thank you. Turning on debugging helped me comb the logs.. finally got this working!
whooohoooo didnt you do well with the replies you got!
But how exactly does YOUR reply help the rest of the poor saps like me who are still struggling for the solution???
whooohoooo didnt you do well with the replies you got!
But how exactly does YOUR reply help the rest of the poor saps like me who are still struggling for the solution???
Well, what's in your logs?
Last edited by Richard Cranium; 07-26-2010 at 09:19 PM.
Reason: Don't post after a 6 pack of beer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.