Re: rpc.lockd infinite loop with Thunar (Xfce)

Unfortunately rpc.lockd is broken and no one has expressed an interest
in working on it. You'll need to set nolockd.

    -Kip

On 4/15/07, Nicolas Blais <nicblais_at_clkroot.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> My /home partition is an nfs export on a server (clk01) and my
> computer (clk02) mounts it at boot so all my users have centralized
> "homes". Everything works as expected there. I have enabled rpc.lockd
> and rpc.statd in my /etc/rc.conf because eclipse and
> openoffice.org-2.2.0 require "true" file locking. When enable, the
> said applications also work as expected.
>
> Having outgrown KDE and gnome and installed Xfce-4.4.1 as my DE, I was
> happy until I found out that when rpc.lockd is enabled, Thunar (the
> file manager) will freeze as rpc.lockd is sent into a seemingly
> infinite loop. Though a kill on rpc.lockd will work, it will break
> anything that requires locking and turn Thunar into an unkillable
> (STOP) state, requiring a reboot.
>
> Here's what I get in my debug.log when both deamons are started with
> "-d 2" flags:
> Apr 15 11:08:21 clk02 rpc.statd: unmon_all for host: NFS NLM prog: 0
> ver: 0 proc: 0
> Apr 15 11:10:40 clk02 rpc.lockd: lock request: V4: write to 192.168.1.10
> Apr 15 11:10:40 clk02 rpc.lockd: nlm4_lock_res from clk01.clkroot.net
> Apr 15 11:10:40 clk02 rpc.lockd: lock answer: pid 883: nlmv4 3
> Apr 15 11:11:00 clk02 rpc.lockd: lock request: V4: write to 192.168.1.10
> Apr 15 11:11:00 clk02 rpc.lockd: nlm4_lock_res from clk01.clkroot.net
> Apr 15 11:11:00 clk02 rpc.lockd: lock answer: pid 883: nlmv4 3
> Apr 15 11:11:20 clk02 rpc.lockd: lock request: V4: write to 192.168.1.10
> Apr 15 11:11:20 clk02 rpc.lockd: nlm4_lock_res from clk01.clkroot.net
> Apr 15 11:11:20 clk02 rpc.lockd: lock answer: pid 883: nlmv4 3
> Apr 15 11:11:40 clk02 rpc.lockd: lock request: V4: write to 192.168.1.10
> Apr 15 11:11:40 clk02 rpc.lockd: nlm4_lock_res from clk01.clkroot.net
> Apr 15 11:11:40 clk02 rpc.lockd: lock answer: pid 883: nlmv4 3
> Apr 15 11:12:00 clk02 rpc.lockd: lock request: V4: write to 192.168.1.10
> Apr 15 11:12:00 clk02 rpc.lockd: nlm4_lock_res from clk01.clkroot.net
> Apr 15 11:12:00 clk02 rpc.lockd: lock answer: pid 883: nlmv4 3
>
> And it will go on forever until a reboot or a kill on both deamons.
> Note that this behavior is only initiated when starting Thunar.
>
> Any guidance appreciated.
>
> Nicolas.
>
> - --
> FreeBSD 7.0-CURRENT #0: Sat Apr  7 15:01:30 EDT 2007
> nicblais_at_clk01.clkroot.net:/usr/obj/usr/src/sys/CLK01
> PGP? : http://plaintext.clkroot.net/security/nicblais.asc
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.3 (FreeBSD)
>
> iD8DBQFGIkm2fxhfsIlaBWsRAjoGAJ9+Ph7UDjHGQWUmf05ARTRcKbiHwgCfRgRO
> 9p2RaHxSas5BIjfZyNGHK5k=
> =HDZ1
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>