userland process rpc.lockd opens untraceable something wrong here?

BBlister bblister at
Thu Feb 21 09:15:31 UTC 2019

Nice explanation, but why the rpcinfo -p does not print all the ports that
rpc.lockd is using? Perhaps rpcinfo is not IPV6 compatible, but can only
locate ipv4 ports? 

The conclusion is that if something is reported by sockstat with '?' in the
process name, this means that the kernel  has opened it. Is this correct?

Thanks again for clarifying this,



Sent from:

More information about the freebsd-hackers mailing list