The weird part is that the filesystem driver actually loads correctly, then autofs hangs when control is returned.
I purposely set the davfs to use the coda device, and the coda device is not functional, so it falls back to the fuse device. The advantage of that, is that is gives some feedback to what is happening. extract from log: May 21 15:56:21 devaccess automount[32663]: lookup_mount: lookup(file): looking up web.site.com May 21 15:56:21 devaccess automount[32663]: lookup_mount: lookup(file): web.site.com -> -fstype=davfs http://v6.muglets.com.dev/repos May 21 15:56:21 devaccess automount[32663]: parse_mount: parse(sun): expanded entry: -fstype=davfs http://v6.muglets.com.dev/repos May 21 15:56:21 devaccess automount[32663]: parse_mount: parse(sun): gathered options: fstype=davfs May 21 15:56:21 devaccess automount[32663]: parse_mount: parse(sun): dequote("http://v6.muglets.com.dev/repos";) -> http://v6.muglets.com.dev/repos May 21 15:56:21 devaccess automount[32663]: parse_mount: parse(sun): core of entry: options=fstype=davfs, loc=http://v6.muglets.com.dev/repos May 21 15:56:21 devaccess automount[32663]: sun_mount: parse(sun): mounting root /home/automount, mountpoint web.site.com, what http://v6.muglets.com.dev/repos, fstype davfs, options May 21 15:56:21 devaccess automount[32663]: open_mount: (mount):cannot open mount module davfs (/usr/lib/autofs/mount_davfs.so: cannot open shared object file: No such file or directory) May 21 15:56:21 devaccess automount[32663]: do_mount: http://v6.muglets.com.dev/repos /home/automount/web.site.com type davfs options using module generic May 21 15:56:21 devaccess automount[32663]: mount_mount: mount(generic): calling mkdir_path /home/automount/web.site.com May 21 15:56:21 devaccess automount[32663]: mount_mount: mount(generic): calling mount -t davfs http://v6.muglets.com.dev/repos /home/automount/web.site.com May 21 15:56:22 devaccess automount[32663]: >> /sbin/mount.davfs: no free coda device to mount May 21 15:56:22 devaccess automount[32663]: >> /sbin/mount.davfs: trying fuse kernel file system May 21 15:56:22 devaccess automount[32663]: >> /sbin/mount.davfs: fuse device opened successfully >From this I deduce that the modules load, and the file system is put in place, and the autofs hangs before control is returned. - kevin _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
