[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
Mon Mar 21 17:38:02 UTC 2016
Doing this forces rpcbind to start on boot and then nis starts
correctly:
# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from /etc/systemd/system/multi-user.target.wants/rpcbind.service to /lib/systemd/system/rpcbind.service
--
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
More information about the foundations-bugs
mailing list