diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-05-06 16:41:05 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2021-05-07 16:43:43 +0200 |
| commit | bbfb8c878c4909fa3de6c735ab84dd6e6158e61f (patch) | |
| tree | 431d60d7f4a53588c3bef4ce7f0da615f5fe4fb5 /src/nss-systemd | |
| parent | 2708160ccda8727de80442cbf634489a360ca001 (diff) | |
| download | systemd-bbfb8c878c4909fa3de6c735ab84dd6e6158e61f.tar.gz | |
userdbd: reverse which path is a socket and which a symlink
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.
Diffstat (limited to 'src/nss-systemd')
0 files changed, 0 insertions, 0 deletions