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

[Martin Dickopp]

On Sat, Dec 23, 2017 at 11:35:44AM +0100, Michael Biebl wrote:
> Am 23.12.2017 um 09:26 schrieb Martin Dickopp:
> > 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.

I removed the entry manually from /etc/passwd and /etc/shadow (with vipw).

> 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?

Yes, this clarification would have helped me. Thanks!

Best regards,
Martin