Bug#885061: systemd-timesyncd.service fails to start if static user is removed, but group is retained

[Michael Biebl]

Am 23.12.2017 um 09:26 schrieb Martin Dickopp:
> Package: systemd
> Version: 236-1
> Severity: normal
> 
> Hi,
> 
> Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz
> 
>   DynamicUser=yes has been enabled for systemd-journal-upload.service,
>   systemd-journal-gatewayd.service and systemd-timesyncd.service.
>   This means we no longer need to statically allocate a systemd-journal-upload,
>   systemd-journal-gateway and systemd-timesync user and you can now safely
>   remove those system users.
> 
> I removed the static systemd-timesync user and rebooted the system, after
> which systemd-timesyncd.service failed to start.
> 
> When I removed the static systemd-timesync group as well, and rebooted
> again, systemd-timesyncd.service worked fine.

Out of interest: which tool did you use to remove the system user?
deluser by default will remove the group along with the user automatically.

That said, I'd be happy to provide a text which clarifies the above.
Would ".. and you can now safely remove those system users along with
their associated groups." be sufficient in your opinion?
If not, would you mind providing an updated text?

-- 
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/20171223/814a3bb1/attachment-0002.sig>