[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

[John Sopko]

IMHO if the rpcbind service is enabled it should just start at boot time
and not have to be self activated.

Found this but no real good solution.

"Regression: rpcbind doesn't start at boottime on systemd controlled
machines."

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167

** Bug watch added: Debian Bug tracker #805167
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1558196

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

Status in nis package in Ubuntu:
  Triaged
Status in rpcbind package in Ubuntu:
  Triaged

Bug description:
  did apt-get update/upgrade  March 16, 2016 
  Description:    Ubuntu Xenial Xerus (development branch)
  Release:        16.04

  rpcbind does not start on boot, tried various systemd debugging steps
  with no clues. After boot systemctl start rpcbind works. There is  a
  /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config
  files which is confusing.

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