
| note that you mistyped "lockd" (aka "lock daemon") as "locd"
Oh, sorry about mistyping
simonpj@cam-05-unx:~/tmp$ ps -Af | grep lockd
root 140 2 0 2016 ? 00:00:00 [kblockd]
simonpj 7882 1184 0 13:22 pts/7 00:00:00 grep lockd
| also, the output of "rpcinfo -p" would be interesting to know
simonpj@cam-05-unx:~/tmp$ rpcinfo -p
Command 'rpcinfo' is available in '/usr/sbin/rpcinfo'
The command could not be located because '/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative privileges associated with your user account.
rpcinfo: command not found
| -----Original Message-----
| From: Herbert Valerio Riedel [mailto:hvriedel@gmail.com]
| Sent: 28 August 2017 12:51
| To: Simon Peyton Jones

Simon Peyton Jones via ghc-devs
| note that you mistyped "lockd" (aka "lock daemon") as "locd"
Oh, sorry about mistyping
simonpj@cam-05-unx:~/tmp$ ps -Af | grep lockd root 140 2 0 2016 ? 00:00:00 [kblockd] simonpj 7882 1184 0 13:22 pts/7 00:00:00 grep lockd
Interesting; no lock daemon.
| also, the output of "rpcinfo -p" would be interesting to know
simonpj@cam-05-unx:~/tmp$ rpcinfo -p Command 'rpcinfo' is available in '/usr/sbin/rpcinfo' The command could not be located because '/usr/sbin' is not included in the PATH environment variable. This is most likely caused by the lack of administrative privileges associated with your user account. rpcinfo: command not found
Silly me; are you able to run `sudo rpcinfo -p`? Cheers, - Ben

sudo rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 56434 status
100024 1 tcp 34797 status
simonpj@cam-05-unx:~/code/HEAD$
| -----Original Message-----
| From: Ben Gamari [mailto:ben@smart-cactus.org]
| Sent: 28 August 2017 13:36
| To: Simon Peyton Jones

Simon Peyton Jones
sudo rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 56434 status 100024 1 tcp 34797 status simonpj@cam-05-unx:~/code/HEAD$
Hmm, interesting. So it seems almost certain at this point that you are not running the lock daemon. In contrast, on an NFSv3 client that I setup I see, $ sudo rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 42146 status 100024 1 tcp 44535 status 100021 1 udp 33470 nlockmgr 100021 3 udp 33470 nlockmgr 100021 4 udp 33470 nlockmgr 100021 1 tcp 40385 nlockmgr 100021 3 tcp 40385 nlockmgr 100021 4 tcp 40385 nlockmgr Hmmm. I'll need to do some reading at this point. Cheers, - Ben

On Mon, Aug 28, 2017 at 1:42 PM, Ben Gamari
Hmm, interesting. So it seems almost certain at this point that you are not running the lock daemon. In contrast, on an NFSv3 client that I setup I see,
This is moderately likely to be common: many people incorrectly believe the lock manager is a server-only daemon, and reliance on file locking is uncommon enough that they are rarely disabused of this belief. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
participants (3)
-
Ben Gamari
-
Brandon Allbery
-
Simon Peyton Jones