On September 12, [email protected] wrote:
> >>>>> "Neil" == Neil Brown <[email protected]> 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.
In all other kernels, lockd is started on demand, either when nfsd
starts or when an nfs filesystem is mounted (without -o nolocks).
NeilBrown
-------------------------------------------------------
In remembrance
http://www.osdn.com/911/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Thu, Sep 12, 2002 at 02:49:27PM +1000, Neil Brown wrote:
> On September 12, [email protected] wrote:
> > >>>>> "Neil" == Neil Brown <[email protected]> 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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs