Ian Kent <raven@xxxxxxxxxx> writes: > On Mon, 2011-09-05 at 19:02 +0200, Miklos Szeredi wrote: >> >> If automounting on lstat(2) is the correct behavior (is it? why?) then at >> least it should be enabled by a global switch or mount option, IMO. > > Ideally we wouldn't need to take special precautions for these > operations at all but we can't, especially for GUI environments that > constantly scan file systems on mount/umount activity. > > Historically for autofs, neither stat(2) or lstat(2) would trigger a > mount. With the current implementation stat(2) now does but lstat(2) > doesn't which is a step in the right direction IMHO. So, I recommend we > continue to encourage user space to make the needed changes so we > continue to move in the right direction, and yes, I acknowledge it is a > pain but it'll never get done otherwise. I'm not quite convinced. What's the advantage of triggering automount on stat(2)? Has anybody complained that stat(2) on the mountpoint doesn't cause an automount? Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
