Hi !
I have some trouble using autofs with Slackware64 13.0
I use the alien's script :
http://connie.slackware.com/~alien/r...ipts/rc.autofs

Here's my auto.master :
/mnt/autofs /etc/auto.misc --timeout 20

Here's my auto.misc :
local -defaults,ro,noatime,tcp,acregmin=60 server:/exports/local
www -defaults,ro,noatime,tcp,acregmin=10 server:/exports/www

First problem : both are mounted as boot.
Second problem : they stay mounted.
As mounted, i mean visible in /proc/mounts
Sometimes, only one is mounted, and the second is activated when i click inside the folder.

Another thing, i made a symlink from /mnt/autofs/local to /usr/local, and i wonder if it can cause trouble.

Is the timeout really in seconds ?

EDIT :
Here's my /proc/mounts
automount(pid1478) on /mnt/autofs type autofs (rw,relatime,fd=5,pgrp=1478,minproto=2,maxproto=3)
server:/exports/local on /mnt/autofs/local type nfs (ro,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,acregmin=60,hard,proto=tcp,timeo=600,retra ns=2,sec=sys,mountaddr=192.168.1.15,mountvers=3,mountproto=tcp,addr=192.168.1.15)
server:/exports/www on /mnt/autofs/www type nfs (ro,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,acregmin=10,hard,proto=tcp,timeo=600,retra ns=2,sec=sys,mountaddr=192.168.1.15,mountvers=3,mountproto=tcp,addr=192.168.1.15)

I really don't know why Pat hasn't upgraded the autofs version that he ships with Slackware. I've had to build and install autofs 4.1.4 at work to get something that actually worked.

Summarising this LQ thread ...

The Slackware 13.0's version of automounter pre-dates support for --timeout in auto.master.The workaround is to use automount's timeout option when starting the daemon. This is not as nice as having it as an option in the map files because it uses the same timeout for all maps; that was OK for me. If that's a problem for you, bathory posted a very nice script that gives different timeouts in the linked thread.

In Slackware 13.1 (still called -current at the moment) you will find autofs-5.0.5

Eric

1 members found this post helpful.

In 13.0, this is indeed, a little outdated :^)

/var/log/packages/autofs-3.1.7-x86_64-1

http://slackware.at/data/slackware64...urce/n/autofs/
autofs-3.1.7.tar.bz2 2000-Nov-04 08:05:24

Do you think i can use this -current package on my 13.0 ?
Anyway, i'll try on a non-production machine right now.
Keep in touch.

EDIT :
As autofs is not network-centric, is the /n series the right place for it to be ?

1 members found this post helpful.

Ouch !

bash-3.1# sh rc.autofs start
Starting automounter: /mnt/nfs/usr/sbin/automount: /usr/lib64/libxml2.so.2: no version information available (required by /usr/sbin/automount)
/usr/sbin/automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required.

bash-3.1# uname -r
2.6.33.2

Will try to build.

EDIT :
Compiled -current version from sources :

###alien's script
bash-3.1# sh rc.autofs start
Starting automounter: /mnt/nfs/usr/sbin/automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required.

Well have no V5.00 in my kernel settings...

EDIT 2 :
###.new script from -current selfbuilt package
bash-3.1# sh /etc/rc.d/rc.autofs.new start
Starting automount:
Error: autofs kernel module is loaded, autofs4 required

EDIT 3 :
bash-3.1# rmmod autofs
bash-3.1# modprobe autofs4
bash-3.1# sh /etc/rc.d/rc.autofs.new start
Starting automount: done.
bash-3.1#

Ok now it works. Let's see if it auto-umounts on this test machine without symlinks.
Hope default timeout isn't two days :^)

EDIT 4 :
Umounted !!!
Going for my production machine with "more advanced settings"

EDIT 5 :
Working too on my production machine.
autofs4 module well started.
Unfortunately, i still have the same problem.
Strangely, at the first cat /proc/mounts, i see only /mnt/autofs/local
At the second i see /mnt/autofs/www too
Now i wait and hope for umount.

EDIT 6 :
umount worked !!!
Now i have to figure out why shares are pre-mounted, as this is the thing i absolutely want to avoid.

EDIT 7 :
I saw only one share mounted this time, which disappeared very quickly.
I don't like this non-slack randomness and i wonder if it's the normal way autofs works, i mean, mounting things very quickly, then umounting.