From: "H. J. Lu" <hjl@lucon.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Adrian Phillips <a.phillips@met.no>, nfs@lists.sourceforge.net
Subject: Re: Lock recovery doesn't work in debian statd/lockd ordering
Date: Fri, 13 Sep 2002 09:37:20 -0700 [thread overview]
Message-ID: <20020913093720.A32168@lucon.org> (raw)
In-Reply-To: <15744.7383.324897.912595@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, Sep 12, 2002 at 02:49:27PM +1000
On Thu, Sep 12, 2002 at 02:49:27PM +1000, Neil Brown wrote:
> On September 12, a.phillips@met.no wrote:
> > >>>>> "Neil" == Neil Brown <neilb@cse.unsw.edu.au> writes:
> >
> > Neil> I just noticed that lock recovery doesn't work with a
> > Neil> Debian NFS server. i.e. server shuts down, restarts, and
> > Neil> the client *Doesn't* reclaim the locks.
> >
> > Um, which version ? On my woody box lockd is started in nfs-common
> > after statd still though :-
>
> /sbin/rpc.lockd is an aberation that only applies to a small range of
> kernels, about 2.2.14 to 2.2.17 I think.
>
Just for the record, I have a need to run the nlockmgr service at a
fixed port. I have
nlockmgr 3003/tcp
nlockmgr 3003/udp
in my /etc/services. But I have to hard code it in my kernel. No, I
don't use kernel modules. It will be nice to for rpc.lockd to passes
the port number to kernel. It doesn't have to start lockd.
H.J.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-09-13 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 2:19 Lock recovery doesn't work in debian statd/lockd ordering Neil Brown
2002-09-12 4:00 ` Adrian Phillips
2002-09-12 4:49 ` Neil Brown
2002-09-13 16:37 ` H. J. Lu [this message]
2002-09-13 19:22 ` Philippe Troin
2002-09-15 21:44 ` Chip Salzenberg
2002-09-16 1:31 ` unsubcribe Will Stowe
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=20020913093720.A32168@lucon.org \
--to=hjl@lucon.org \
--cc=a.phillips@met.no \
--cc=neilb@cse.unsw.edu.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.