From: Olaf Kirch <okir@suse.de>
To: Gavin Hamill <gdh@acentral.co.uk>
Cc: nfs@lists.sourceforge.net
Subject: Re: lockd / statd fun (sorry)
Date: Tue, 27 Apr 2004 17:32:00 +0200 [thread overview]
Message-ID: <20040427153200.GC6836@suse.de> (raw)
In-Reply-To: <20040427134343.GB1330@acentral.co.uk>
On Tue, Apr 27, 2004 at 02:43:43PM +0100, Gavin Hamill wrote:
> OK, I'm assuming here that statd is only run by the machine running nfsd and
> exporting filesystems, and /usr/sbin/rpc.statd is definately in the process list
No, statd needs to run on the client as well.
> Moving onto the files in /var/lib, everything seems to be in order, but I never see any
> files written to /var/lib/nfs/sm.
Files should appear in /var/lib/nfs/sm while a lock is held, and disappear
shortly after the lock is released.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-04-27 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 10:37 lockd / statd fun (sorry) Gavin Hamill
2004-04-23 11:32 ` Bernd Schubert
2004-04-23 11:48 ` Gavin Hamill
2004-04-23 11:57 ` Olaf Kirch
2004-04-27 13:43 ` Gavin Hamill
2004-04-27 15:32 ` Olaf Kirch [this message]
2004-04-27 15:47 ` Gavin Hamill
2004-04-27 15:56 ` Olaf Kirch
2004-04-27 16:49 ` Trond Myklebust
2004-04-27 18:15 ` Gavin Hamill
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=20040427153200.GC6836@suse.de \
--to=okir@suse.de \
--cc=gdh@acentral.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox