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

John Sopko 1558196 at bugs.launchpad.net
Fri Mar 18 18:35:55 UTC 2016


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
Server Team, 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

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



More information about the Ubuntu-server-bugs mailing list