On Fri, 25 Aug 2006, Matt Bernstein wrote: > At 09:29 +0800 Ian Kent wrote: > > > On Thu, 24 Aug 2006, Matt Bernstein wrote: > > > +/* 'what' may itself be on an automounted file system so we need to > > > access it */ > > > +/* to ensure it gets mounted before calling wait_for_lock() inorder to > > > avoid a*/ > > > +/* long delay */ > > > + (void)access(what,F_OK); > > > > That can lead to corruption of /etc/mtab. > > That's why the lock was introduced. > > > > In v5 the locking can be disabled as most people have updated mount(8) these > > days. > > Thanks--is the locking disabled, or do we need to patch the source? (I haven't > looked at it yet.) > > > Someone else has reported that bind mounts aren't working with v5. > > It would be good to resolve this but I need more info. > > A debug log would be best. > > I set DEFAULT_LOGGING="debug" in /etc/sysconfig/autofs (this is > autofs-5.0.1-0.rc1.16.x86_64 in FC6test), and I got this in /var/log/messages: > > Aug 25 07:31:29 laurel automount[17274]: attempting to mount entry /homes/mb > Aug 25 07:31:29 laurel automount[17274]: mount_mount: mount(nfs): no hosts > available
Mmmm ... I shouldn't be defaulting to NFS for a ":" escaped mount. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
