Dan, thanks for the comments, appreciate it. In reply: Using only "compat" in /etc/nsswitch.conf is legitimate and we use it without issue on multiple Linux distributions as well as older Ubuntu releases. It invokes a different behaviour to using "nis", allowing more fine grained control of who can authenticate from the NIS database by appending +user|+netgroup to /etc/passwd. FWIW, replacing "compat" with "nis" and removing the + entries at the end of the passwd file yields the same systemd behaviour. Earlier in testing I tried using sssd, going direct to AD, cutting out NIS entirely. Using sssd also failed to start the systemd user context. I will try that again tomorrow with the debug flags to see that shows up anything new.
getent passwd amcvey responds immediately and correctly, suggesting the underlying calls to getpwnam() are also working correctly. All other NIS accounts are also resolved correctly and without delay. I don't think using nscd will help much here, the issue is not the response time from the NIS server(s) or the number of calls being made. This also makes me think that the bug you referenced (https://github.com/systemd/systemd/issues/12702) is not the root cause here, as there are performance issues in that use case, which I'm not seeing here at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915502 Title: "systemd --user" fails to start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
