Thanks for the further investigation, taraijpn.
Indeed, I was able to (1) reproduce the scenario reported in the
description, and (2) confirm that adding the "-r" option to
/etc/default/rpcbind's OPTION variable will make the service run as the
reporter expected.
I appreciate the time Rafael spent on this bug and his conclusions; it
was easy to verify the scenario following his comments.
Having said all that, I consider that this is not a bug, and is properly
documented in the manpages. I am therefore setting the status of this
bug to Invalid; feel free to change it back to New and to provide more
information if you disagree with this decision.
Thank you.
** Changed in: rpcbind (Ubuntu)
Status: Confirmed => Invalid
** Changed in: rpcbind (Ubuntu Eoan)
Status: Confirmed => Invalid
** Changed in: rpcbind (Ubuntu Focal)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890276
Title:
rpcbind changes after bionic broke rup broadcast feature
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1890276/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
