On Mon, 2018-01-01 at 21:55 +0800, Ed Greshko wrote:
On 01/01/18 20:31, Patrick O'Callaghan wrote:
> On Mon, 2018-01-01 at 12:04 +0800, Ed Greshko wrote:
> > On 01/01/18 11:32, Sam Varshavchik wrote:
> > > My rpcbind service seemed to have been enabled in 2011. Its current vendor
preset
> > > is "disabled". So, I guess, it wouldn't be enabled today, by
default. Was it
> > > enabled by default in 2011? No idea. What does disabling it would mean,
with
> > > respect to libvirt, and any guest VMs? No idea.
> >
> > Well, on the one system where I run VM's under virt-manager I don't
have rpcbind
> > enabled or running and the VM's run just fine. That system is a fresh F27
install
> > with only KDE as the desktop.
>
> I have a similar system (F27, KDE, Windows 10 under KVM/QEMU) and
> rpcbind is running. However I haven't reinstalled this system in years,
> just updated it, so I've no idea why it's running. In fact I didn't
> even notice it was before reading this thread.
>
I suppose it may be interesting to know what "rpcinfo" returns.
$ rpcinfo
program version netid address service owner
100000 4 tcp6 ::.0.111 portmapper superuser
100000 3 tcp6 ::.0.111 portmapper superuser
100000 4 udp6 ::.0.111 portmapper superuser
100000 3 udp6 ::.0.111 portmapper superuser
100000 4 tcp 0.0.0.0.0.111 portmapper superuser
100000 3 tcp 0.0.0.0.0.111 portmapper superuser
100000 2 tcp 0.0.0.0.0.111 portmapper superuser
100000 4 udp 0.0.0.0.0.111 portmapper superuser
100000 3 udp 0.0.0.0.0.111 portmapper superuser
100000 2 udp 0.0.0.0.0.111 portmapper superuser
100000 4 local /run/rpcbind.sock portmapper superuser
100000 3 local /run/rpcbind.sock portmapper superuser
poc