← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1890276] Re: rpcbind changes after bionic broke rup broadcast feature

 

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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1890276

Title:
  rpcbind changes after bionic broke rup broadcast feature

Status in rpcbind package in Ubuntu:
  Invalid
Status in rpcbind source package in Xenial:
  Fix Released
Status in rpcbind source package in Bionic:
  Fix Released
Status in rpcbind source package in Eoan:
  Invalid
Status in rpcbind source package in Focal:
  Invalid

Bug description:
  When I call inetd services rup or rusersd in broadcast mode, I get
  answers from my Ubuntu 18.04 machines only. An Ubuntu 20.04 machine
  (here rzpc101) answers only when addressed directly:

  zierke@rzpc100$ rup
  rzpc100.informatik.un 14:02 up  10 days,    8:30, load 0.52 0.38 0.23
  rzlinux.informatik.un 14:02 up    1 day,    3:12, load 0.04 0.09 0.03
  rzpc174.informatik.un 14:02 up   4 days,   19:28, load 0.00 0.01 0.00
  ^C
  zierke@rzpc100$ rup rzpc101
  rzpc101.informatik.un 14:02 up              3:29,   3 users, load 0.33 0.32 0.15
  zierke@rzpc100$ rusers
  rzpc100.informatik.u zierke zierke 
  rzlinux.informatik.u zierke zierke zierke 
  ^C
  zierke@rzpc100$ rusers rzpc101
  rzpc101.informatik.u zierke zierke zierke 

  zierke@rzpc101$ lsb_release -rd
  Description:	Ubuntu 20.04.1 LTS
  Release:	20.04

  zierke@rzpc100$ lsb_release -rd
  Description:	Ubuntu 18.04.4 LTS
  Release:	18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openbsd-inetd 0.20160825-4build1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  4 14:03:06 2020
  InstallationDate: Installed on 2020-07-24 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openbsd-inetd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1890276/+subscriptions