Re: Woody & autofs
hi ya david
if you are on crir-a136.univ-savoie.fr...
i am assuming oyu do want to automount the local /data/etc.tgz to itself
and unmount when not in use...
when you manually mount /data ... what files do you see
that is not visible when automounting with autofs ??
i am assuming your mchine only has one file
crir-a136.univ-savoie.fr:/data/etc.tgz
than your ls -la /autofs shows the correct result
and your ls -la /autofs/data showed the correct result
or ls -la /autofs/* will show the same result above
if you were expecting more than etc.tgz to be listed,
than we'd need to find out what else is missing/broken
( probably a permission problem ob the other files
have fun
alvin
http://www.Linux-Consulting.com/Amd_AutoFS - AutoFS-HOWTO
On Fri, 23 Nov 2001, David Berard wrote:
>
> Hello,
>
> Anyone is using autofs with woody on a SMP computer ?
>
> I have try with a kernel 2.2.19 and 2.4.13 with no luck. I don't
> understand why it does not work.
>
> I export a directory with NFS on the host. I can mount this directory via
> a mount command (mount -t nfs crir-a136:/data /mnt), with autofs, I have
> no error, but the autofs mount doesn't work correctly (I think).
>
> This is my /etc/exports :
>
> # /etc/exports: the access control list for filesystems which may be
> # exported
> # to NFS clients. See exports(5).
> /data crir-a136.univ-savoie.fr(rw) 127.0.0.1(rw)
>
> This is my /etc/auto.master
>
> # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $
> # Sample auto.master file
> # Format of this file:
> # mountpoint map options
> # For details of the format look at autofs(5).
> #/var/autofs/misc /etc/auto.misc
> /autofs /etc/auto.test
>
> This is my /etc/auto.test
>
> data -rw,fstype=nfs crir-a136.univ-savoie.fr:/data
>
>
> When I start autofs (/etc/init.d/autofs start), I obtain this logs in
> daemon.log :
>
> Nov 22 23:40:09 crir-a136 rpc.statd[164]: Version 0.3.3 Starting
> Nov 22 23:40:10 crir-a136 automount[185]: starting automounter version
> 3.1.7, path = /autofs, maptype = file, mapname = /etc/auto.test
> Nov 22 23:40:10 crir-a136 automount[185]: Map argc = 1
> Nov 22 23:40:10 crir-a136 automount[185]: Map argv[0] = /etc/auto.test
> Nov 22 23:40:10 crir-a136 automount[185]: mount(bind): Testing if "mount
> --bind" works correctly...
> Nov 22 23:40:10 crir-a136 automount[185]: mount(bind): calling mount
> --bind /tmp/autofs-bind-3bfd7eca-b9/dir1 /tmp/autofs-bind-3bfd7eca-b9/dir2
> Nov 22 23:40:10 crir-a136 automount[185]: using kernel protocol version 3
>
>
> If I make a ls of the mount point of the indirect map, I obtain no file.
>
> crir-a136:/etc# ls -la /autofs/
> total 4
> drwxr-xr-x 2 root root 0 Nov 23 10:35 .
> drwxr-xr-x 23 root root 4096 Nov 23 10:32 ..
>
>
> If I make a ls of one of the directory of the indirect map, this is OK...
> Is-it normal ?
>
> crir-a136:/etc# ls -la /autofs/data
> total 504
> drwxrwsr-x 3 root staff 4096 Nov 22 16:15 .
> drwxr-xr-x 3 root root 0 Nov 23 10:35 ..
> -rw-r--r-- 1 root staff 489440 Nov 22 16:15 etc.tgz
> drwxr-xr-x 2 root root 16384 Nov 22 13:01 lost+found
>
> Can you tell me what I miss, or what I misundertood ?
>
> P.S. Sorry for my english, but it's not my primary language.
Reply to: