[didn't think to subscribe to this bug, so I didn't see this until now]
On Thu, 24 Dec 2015 10:57:02 +0100 Laurent Bigonville wrote:
> > nis can't be the only rpc service that talks to rpcbind over inet rather
> > than unix sockets, and custom rpc services are probably more likely
> > to use inet
> nis can't be the only rpc service that talks to rpcbind over inet rather
> than unix sockets, and custom rpc services are probably more likely
> to use inet. The path of least surprise is clearly to start rpcbind
> on inet socket access as well.
>
> You could argue that it should only start on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nis can't be the only rpc service that talks to rpcbind over inet rather
than unix sockets, and custom rpc services are probably more likely
to use inet. The path of least surprise is clearly to start rpcbind
on inet socket access as well.
You could a
3 matches
Mail list logo