On Mon, 2018-01-01 at 09:19 -0500, Tom H wrote: > On Sun, Dec 31, 2017 at 10:32 PM, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> 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. > > > > ... Hold on a second. Digging through Wikipedia, Fedora 16 was released a > > week before the rpcbind's enabling timestamp on my server. > > > > Grabbed > > https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/16/Fedora/x86_64/os/Packages/rpcbind-0.2.0-15.fc16.x86_64.rpm > > > > postinstall scriptlet (using /bin/sh): > > if [ $1 -eq 1 ] ; then > > # Initial installation > > /bin/systemctl enable rpcbind.service >/dev/null 2>&1 || : > > fi > > > > Well, that answers that. Happy New Year, everyone! > > rpcbind should not enable itself: > > https://bugzilla.redhat.com/show_bug.cgi?id=1087951 Thanks, I added a comment to the BZ report and disabled rpcbind.service, however it's also necessary to disable and stop rpcbind.socket. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
