Hide Forgot
i am tired having to disable the socket with each and every update since "rpcbind" itself is only used *if* i start the NFS service for VMware backups with "nfs-start.sh" [root@srv-rhsoft:~]$ systemctl disable rpcbind.socket; systemctl stop rpcbind.socket Removed symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket. Apr 07 00:22:06 INFO Upgraded: rpcbind-0.2.3-7.rc1.fc23.x86_64 Apr 7 00:22:05 srv-rhsoft systemd: Listening on RPCbind Server Activation Socket. Apr 7 00:22:05 srv-rhsoft systemd: Starting RPCbind Server Activation Socket. Apr 7 00:22:06 srv-rhsoft systemd: Stopping RPCbind Server Activation Socket. Apr 7 00:22:06 srv-rhsoft systemd: Listening on RPCbind Server Activation Socket. Apr 7 00:22:06 srv-rhsoft systemd: Starting RPCbind Server Activation Socket. Apr 7 00:22:07 srv-rhsoft systemd: Stopping RPCbind Server Activation Socket. Apr 7 00:22:07 srv-rhsoft systemd: Listening on RPCbind Server Activation Socket. Apr 7 00:22:07 srv-rhsoft systemd: Starting RPCbind Server Activation Socket.
DAMNED stop it - and no mask them won't work if you just have the packages installed and configured to mount a LUKS encrypted external backup disk and share it over NFS to start virtual servers in case of emergency from there when i say "systemctl disable" i mean that and *nobody* has a business to fire "systemctl enable" at every random update
rpcbind-0.2.3-11.rc1.fc24.x86_64 still enables rpcbind.socket. Please also remove systemctl-enable commands, or use systemctl-preset command in the trigger scripts. I do not understand why such trigger scripts are necessary in the first place. ==== %triggerun -- rpcbind < 0.2.0-15 %{_bindir}/systemd-sysv-convert --save rpcbind >/dev/null 2>&1 ||: /bin/systemctl --no-reload enable rpcbind.service >/dev/null 2>&1 /sbin/chkconfig --del rpcbind >/dev/null 2>&1 || : /bin/systemctl try-restart rpcbind.service >/dev/null 2>&1 || : %triggerin -- rpcbind > 0.2.2-2.0 /bin/systemctl enable rpcbind.socket >/dev/null 2>&1 || : /bin/systemctl restart rpcbind.socket >/dev/null 2>&1 || :
rpcbind-0.2.3-8.rc1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d4ae4edcbb
rpcbind-0.2.3-11.rc1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d5ed976bf1
rpcbind-0.2.3-11.rc1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d5ed976bf1
rpcbind-0.2.3-8.rc1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d4ae4edcbb
rpcbind-0.2.3-11.rc1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
today rpcbind.x86_64 0.2.3-11.rc2.fc24 landed in updates-testing and that bullshit still happened - so what is here "Status: ON_QA -> CLOSED" [root@srv-rhsoft:~]$ systemctl disable rpcbind.socket Removed symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket
*** This bug has been marked as a duplicate of bug 1393721 ***