Date: Thu, 21 Feb 2019 02:15:28 -0700 (MST) From: BBlister <bblister@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: userland process rpc.lockd opens untraceable ports...is something wrong here? Message-ID: <1550740528377-0.post@n6.nabble.com> In-Reply-To: <877baa2abd2c062a389b88e66dd67f1fba032e93.camel@freebsd.org> References: <1550610819543-0.post@n6.nabble.com> <CAOjFWZ7kJoa-_EVBrLUwLrs9J7ERWqkRf4bZh_giQ4-NRrGS_w@mail.gmail.com> <7b44b3ce-9b96-e91b-b9ca-57100c784db7@sentex.net> <20190219220404.GA1668@troutmask.apl.washington.edu> <1550671337578-0.post@n6.nabble.com> <877baa2abd2c062a389b88e66dd67f1fba032e93.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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, Rgz, BB -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-hackers-f4034256.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1550740528377-0.post>