post ino64: lockd no runs?

David Wolfskill david at catwhisker.org
Mon Jun 12 12:14:45 UTC 2017


On Mon, Jun 12, 2017 at 12:24:58AM -0700, Xin Li wrote:
> Thanks for Kostantin's hints, this is indeed related to my change (which
> exposed an old bug with rpc.lockd).
> 
> Please try attached fix.
> ....

Aye; that appears to do the job:

freebeast(11.1)[1] uname -a && service lockd status
FreeBSD freebeast.catwhisker.org 11.1-BETA1 FreeBSD 11.1-BETA1 #367  r319823M/319852:1100514: Mon Jun 12 04:58:48 PDT 2017     root at freebeast.catwhisker.org:/co
mmon/S3/obj/usr/src/sys/GENERIC  amd64
lockd is running as pid 602.
freebeast(11.1)[2] 

Thanks! :-)

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Trump (et al.): Hiding information doesn't prove its falsity.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170612/7caadffc/attachment.sig>


More information about the freebsd-stable mailing list