Bug#950822: systemd-sysusers hangs if nis is enabled in a systemd-nspawn container

[Ryutaroh Matsumoto]

Control: tags -1 + fixed - moreinfo
Control: retitle -1 Fix found: systemd-sysusers hangs if nis is
enabled in a systemd-nspawn container

I found a solution (or a workaround).

The problem is that
(1) systemd-sysusers  tries to use Sun RPC (TCP connection to 127.0.0.1:111)
  in a nis enabled container.
(2) at that time, rpcbind.socket is ready (by systemd), and
(3) rpcbind.service is not ready, because rpcbind.service depends on
  systemd-sysusers.service.
(4) Then systemd-sysusers communication to 127.0.0.1:111 get stuck.

When I made

[Unit]
Before=rpcbind.socket
as /etc/systemd/system/systemd-sysusers.service.d/my.conf

OR

[Unit]
After=systemd-sysusers.service
as /etc/systemd/system/rpcbind.socket.d/my.conf

Then the problem goes away!!!

Anyway, the current dependency
rpcbind.socket -> systemd-sysusers.service -> rpcbind.service
looks nonsense.

The remaining problem is where the above nonsense order of
dependency should be fixed, rpcbind Debian package or the systemd
upstream...

Best regards, Ryutaroh