On Wed, 2006-09-20 at 15:00 +0000, jack snodgrass wrote: > Ian Kent <raven <at> themaw.net> writes: > > > > Don't think so. > > Do you have any monitoring on this box. > > I've had situations where health monitoring (network monitoring believe > > it or not) was scanning directories. > > > > Do you have hal installed? > > What version is it? > > > > Does the problem go away if you do a > > /etc/init.d/hald stop > > > > Basically we need to find out what is causing accesses to the > > filesystems. > > > > Ian > > > > There are two issues... I should not have mentioned the 15 minute > thing.... the first / main issue was posted in my first message > today... you'll see i tested this on a stand-a-lone box and I > mounted /opt ( which was not part of my autofs stuff ) and all > of my autofs mounts were mounted. ... I did a bit more checking > and there is a symbolic link on /opt: > /opt/store/link_to_autofs_fs_directory > that would ( maybe ) explain why one of the autofs mounts gets > mounted when I mount /opt. It doesn't explain why ALL of the autofs > mounts occur.
Yep. That will certainly mount /myth/store, as it should, but I don't know why the other mounts are being mounted. I don't have any other similar reports and the autofs version you are using has been current for quite a while now. As for the kernel, the autofs4 stuff in it has also been there for quite a while. I'll have a go at trying to reproduce it as soon as I get some time. Sorry I can't be more helpful. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
