Am 06.08.19 um 15:35 schrieb Felipe Sateler:> > > On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl <bi...@debian.org
> # systemctl restart rpcbind.service rpcbind.socket > > Job for rpcbind.socket failed. > See "systemctl status rpcbind.socket" and "journalctl -xe" for details. > A dependency job for rpcbind.service failed. See 'journalctl -xe' for > details. > > This needs further investigation, where the underlying problem is. > For the time being, I would suggest a different workaround, ie. > restarting rpcbind.service and rpcbind.socket sequentially (or only > rpcbind.service, I think that should be sufficient) > > > So somehting like this: > override_dh_installsystemd: >  dh_installsystemd rpcbind.socket > dh_installsystemd rpcbind.service > > > I'm not yet sure if this is a bug in systemd itself, in rpcbind or > debhelper for generating such a code sequence, so CCing all affected > parties. > > > The idea was to let systemctl/systemd order the jobs in whatever way it > saw fit, according to the ordering requirements of the units. If there > is a bug somewhere, it is either in systemd, or in rpcbind where an > ordering requirement is missing. In other words I guess your point is, that this is a bug in systemd/systemctl? > Does the problem persist if you add After=rpcbind.socket to rpcbind.service? I think the After= ordering is implied for socket units, see man systemd.socket Implicit Dependencies The following dependencies are implicitly added: • Socket units automatically gain a Before= dependency on the service units they activate. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature