From: Craig Small <csmall@enc.com.au>
To: nfs@lists.sourceforge.net
Subject: Re: NFS and fuser
Date: Mon, 29 May 2006 11:39:38 +1000 [thread overview]
Message-ID: <20060529013938.GA2392@enc.com.au> (raw)
In-Reply-To: <17530.15683.868564.165086@cse.unsw.edu.au>
On Mon, May 29, 2006 at 10:16:03AM +1000, Neil Brown wrote:
> Presumably 'fuser' should only report files/directories that are
> actually 'open' inside the kernel. Thus 'showmount -e' is
> not appropriate.
Yes, that's right. The typical use for it is when you are trying to
unmount a drive and it is in use, you want to know what is using it.
You don't really care what might use it, or at least if you do it is
not fuser's job to tell you.
> I stand by my asserting that examining /proc/fs/nfs/exports is the
> best thing to do.
That's good enough for me! Thanks for your time.
- Craig
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer
csmall at : enc.com.au ieee.org debian.org
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-05-29 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 23:13 NFS and fuser Craig Small
2006-05-28 23:43 ` Neil Brown
2006-05-28 23:54 ` Craig Small
2006-05-29 0:16 ` Neil Brown
2006-05-29 1:39 ` Craig Small [this message]
2006-05-29 11:47 ` Yi.Xiong
2006-05-29 12:10 ` Neil Brown
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=20060529013938.GA2392@enc.com.au \
--to=csmall@enc.com.au \
--cc=nfs@lists.sourceforge.net \
/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.