From: Craig Small <csmall@enc.com.au>
To: nfs@lists.sourceforge.net
Subject: NFS and fuser
Date: Mon, 29 May 2006 09:13:20 +1000 [thread overview]
Message-ID: <20060528231319.GA31396@enc.com.au> (raw)
Hello,
I am the current maintainer of the psmisc package, which includes a
program called fuser. fuser lets someone work out which process has
opened a "file", using a wide meaning for the word file. I currently
have a NFS-related bug which I'm hoping the list can help me with.
The problem is if knfsd exports a directory out, it does not show
up in its /proc/<pid>/fd/ directory. I am looking for a nice clean way
of determining what directories knfsd has exported. It appears for
example that /proc/fs/nfs/exports does not appear in all versions of
Linux.
Another way would be to read /var/lib/nfs/xtab, but I do not know if
this file location is always going to be there.
My main concern is whatever assumptions I make (eg file X is always
located at Y) are reasonable ones.
I'm not on the NFS list so if you could CC me directly that would be
great.
- 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 reply other threads:[~2006-05-28 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 23:13 Craig Small [this message]
2006-05-28 23:43 ` NFS and fuser Neil Brown
2006-05-28 23:54 ` Craig Small
2006-05-29 0:16 ` Neil Brown
2006-05-29 1:39 ` Craig Small
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=20060528231319.GA31396@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.