Bug#931356: libnss-systemd: 'systemd' entry in /etc/nsswitch.conf confuses daemons when systemd is not pid1

[Lorenzo Puliti]

Package: libnss-systemd
Version: 241-5
Severity: normal

Dear systemd maintainers,
I'm testing the systemd --> runit-init switch in a VM (both Virtualbox and Qemu) and i'm running 
into several issues that looks related to libnss-system, for example

* Dbus:
	- Hangs for about 90 sec at boot, same if restarted
	- apt triggers involving bus hangs for a very long time, then
	  fail; apt tries twice than it gives up
* Exim4:
	- hangs for about 50 sec at boot, same for restart
* Avahi-daemon:
	- the sysv scripts exits nonzero at boot with an error
	  'Timeout reached while waiting for return value'
* root VT login:
	- after I provide the right password and hit return, it takes about 25 sec
	  to login

I believe this is part of the same issue already spotted by Martin Pitt in #838480, message #49.
In the VM I have a /etc/nsswitch.conf file that has two lines like this

>passwd:         compat systemd
>group:          compat systemd

and removing 'systemd' (especially the group line) from those line fixes all the above
issues.
Is this 'systemd' module supposed to work when systemd is not active (PID 1) ?
Could you please provide some fix?

Thanks,
Lorenzo

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.20.3-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages libnss-systemd depends on:
ii  libc6    2.28-10
pn  systemd  <none>

libnss-systemd recommends no packages.

libnss-systemd suggests no packages.