Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

[Michael Biebl]

Am 15.01.2018 um 12:57 schrieb Martin Pitt:
> If timesyncd in particular somehow wants to resolve the systemd-timesyncd
> system user in its own code, then that either should be fixed, or systemd needs
> to raise libnss-systemd to a Depends: for that particular bug/reason.

grepping through the code, I get

> $ grep "Cannot resolve user name" -R
> src/timesync/timesyncd.c:                log_error_errno(r, "Cannot resolve user name %s: %m", user);
> src/resolve/resolved.c:                log_error_errno(r, "Cannot resolve user name %s: %m", user);
> src/network/networkd.c:                log_error_errno(r, "Cannot resolve user name %s: %m", user);
> src/network/netdev/tuntap.c:                        return log_netdev_error_errno(netdev, r, "Cannot resolve user name %s: %m", t->user_name);

https://github.com/systemd/systemd/blob/master/src/timesync/timesyncd.c#L116

So it is exactly as you explained.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180115/571fd70a/attachment-0002.sig>