bbfb8c878c
userdbd listens on "two" sockets, that are actually the same: one is a real AF_UNIX socket in the fs, and the other is a symlink to it. So far, when userdbd was started from the command line it would make one a symlink and the other a real socket, but when invoked via unit files they'd be swapped, i.e. the other would be a symlink and the one a real socket. Let's bring this in line. Since the "io.systemd.Multiplexer" is our main interface, let's make it the one exposed as socket, and then make "io.systemd.NameServiceSwitch" a symlink to it. Or in other words, let's adjust the C code to match the unit file.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.