Firefox locking and unkillable

[Andrea Venturoli]

Werner Griessl ha scritto:

> Start the rpc-lockd .
> in /etc/rc.conf:
> rpc_lockd_enable="YES"
> then
> /etc/rc.d/lockd start



On the server I have:

# cat /etc/rc.conf |grep rpc
rpcbind_enable="YES"
rpcbind_flags="-ls"
rpc_statd_enable="YES"
rpc_lockd_enable="YES"

# ps ax|grep rpc
   772  ??  Ss     0:04.55 /usr/sbin/rpcbind -ls
   835  ??  Is     0:04.66 /usr/sbin/rpc.statd
   841  ??  Ss     4:03.49 rpc.lockd: server (rpc.lockd)
   879  ??  I      0:00.00 rpc.lockd: client (rpc.lockd)



On the client:

# cat /etc/rc.conf |grep rpc
rpcbind_enable="YES"
rpcbind_flags="-ls"
rpc_statd_enable="YES"
rpc_statd_flags="-p 918"
rpc_lockd_enable="YES"
rpc_lockd_flags="-p 868"

(Those -p are there to easy ipfw setup).

# ps ax|grep rpc
   561  ??  Is     0:00.03 /usr/sbin/rpcbind -ls
   597  ??  Ss     0:00.00 /usr/sbin/rpc.statd -p 918
   603  ??  Ss     0:00.22 rpc.lockd: server (rpc.lockd)
   611  ??  S      0:00.40 rpc.lockd: client (rpc.lockd)



ipfw is not denying any of these packets.
On the server side I see a lot of these in the logs:

  rpcbind: connect from 10.1.2.18 to getport/addr(nlockmgr)



NFS lockings seems to work fine for everythings else, ranging from KDE 
to compiling some exotic ports.


Is there any tool I can use to debug NFS locking?


  bye & Thanks
	av.