Date: Sun, 4 Jun 2017 22:33:02 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: post ino64: lockd no runs? Message-ID: <YTXPR01MB0189FE08E4851A52CD806BF8DDF50@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <24b27f3e-f91b-553d-f2c1-e876608e0baf@protected-networks.net> References: <24b27f3e-f91b-553d-f2c1-e876608e0baf@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Just fyi, rpc.lockd isn't NFS. It is a separate protocol Sun called NLM and
I didn't ever implement it for what I believed were good reasons.
Hopefully someone who works with the code can help.
Btw, if you don't the locks visible to multiple clients concurrently, you c=
an
just do your mounts with "nolockd" and avoid running it.
Or, you can switch to NFSv4, which does a reasonable job of implementing
locking.
I might take a look at the code, in case I can spot something obvious, but =
I
won't bet on it.
rick
________________________________________
From: Michael Butler <imb@protected-networks.net>
Sent: Sunday, June 4, 2017 8:57:44 AM
To: freebsd-current; Rick Macklem
Subject: post ino64: lockd no runs?
It seems that {rpc.}lockd no longer runs after the ino64 changes on any
of my systems after a full rebuild of src and ports. No log entries
offer any insight as to why :-(
imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB0189FE08E4851A52CD806BF8DDF50>