From: Alexander Viro <aviro@redhat.com>
To: Matthew Booth <mbooth@redhat.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: Identifying writes to NFS
Date: Wed, 30 May 2007 13:56:34 -0400 [thread overview]
Message-ID: <20070530175634.GK27042@devserv.devel.redhat.com> (raw)
In-Reply-To: <1180542928.5055.16.camel@localhost.localdomain>
On Wed, May 30, 2007 at 05:35:28PM +0100, Matthew Booth wrote:
> I'd like to be able to reliably recognise a PATH record which refers to
> an NFS mount. It seems that dev=00:xx would be related to the answer.
> However, each mount seems to have its own value of xx, and other mounts
> not backed by a block device, eg /proc and /dev, also have dev=00:xx.
>
> The answer can't be related to a single system, as the solution has to
> be rolled out across a large estate with a variety of nfs mounts on
> particular servers.
>
> Any ideas? Thanks,
man statfs, look at f_type field there.
next prev parent reply other threads:[~2007-05-30 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 16:35 Identifying writes to NFS Matthew Booth
2007-05-30 17:56 ` Alexander Viro [this message]
2007-05-30 18:06 ` Steve Grubb
2007-05-30 18:11 ` Matthew Booth
2007-05-30 18:11 ` Steve Grubb
2007-05-31 9:34 ` Matthew Booth
2007-05-31 14:44 ` Steve Grubb
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=20070530175634.GK27042@devserv.devel.redhat.com \
--to=aviro@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mbooth@redhat.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.