From: Ian Kent <raven@themaw.net>
To: Chris Walker <cwalker@pixar.com>
Cc: autofs@linux.kernel.org
Subject: Re: determining which process triggered an automount
Date: Thu, 12 Apr 2007 18:05:04 +0800 [thread overview]
Message-ID: <1176372304.3441.63.camel@raven.themaw.net> (raw)
In-Reply-To: <20070411234847.GH21698@pixar.com>
On Wed, 2007-04-11 at 16:48 -0700, Chris Walker wrote:
> I'd like to determine which process triggered an automount. Might I have
> to use Systemtap or some other tool to determine this?
Can't really do that with autofs version 4.
It's a bit of information that the daemon doesn't get in the request
packet from the kernel. This information is passed to the daemon in
autofs version 5 and is logged when debug logging is enabled so you
could try that.
Sorry I can't be more help.
Ian
next prev parent reply other threads:[~2007-04-12 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 23:48 determining which process triggered an automount Chris Walker
2007-04-12 10:05 ` Ian Kent [this message]
2007-04-12 14:13 ` Peter C. Norton
2007-04-13 4:20 ` Fabio Olive Leite
2007-04-13 5:22 ` Chris Walker
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=1176372304.3441.63.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=cwalker@pixar.com \
/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.