Simon Peyton Jones <simo...@microsoft.com> writes:

> 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

Attachment: signature.asc
Description: PGP signature

_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Reply via email to