From: Ian Kent <raven@themaw.net>
To: Julian Hagenauer <chaosbringer@gmx.de>
Cc: autofs@linux.kernel.org
Subject: Re: NFS+AUTOFS: Strange connections every 2 minutes
Date: Tue, 07 Nov 2006 20:46:21 +0800 [thread overview]
Message-ID: <1162903581.18975.48.camel@localhost> (raw)
In-Reply-To: <20061107133602.692531bb@notebook.chaosbringer.de>
On Tue, 2006-11-07 at 13:36 +0100, Julian Hagenauer wrote:
> > It could be something else but experience so far has shown that this is
> > caused by some process continually accessing mount points. Unless there
> > is other evidence I can only recommend you find the process that's
> > scanning the directory tree or trying to access your automount
> > directories and fix it.
>
> Hi,
> thank you, that could really be the problem. Do you have any hind, how i could determine that process?
Not really, with version 4. Some investigation with "lsof" might help.
The pid of the requesting process has been added to the kernel
communications structure and is recorded in the debug log for version 5
for this very reason.
Ian
prev parent reply other threads:[~2006-11-07 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 9:51 NFS+AUTOFS: Strange connections every 2 minutes Julian Hagenauer
2006-11-07 12:06 ` Ian Kent
2006-11-07 12:36 ` Julian Hagenauer
2006-11-07 12:46 ` Ian Kent [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1162903581.18975.48.camel@localhost \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=chaosbringer@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.