Bug#918190: systemd: timesyncd stopped updating clock file after package update

[Patrick Häcker]

Hello,
 
> Can you post the output of
> ls -ld /var/lib/systemd/timesync
> ls -la /var/lib/private/systemd/

root at mmm /h/pat# ls -ld /var/lib/systemd/timesync
lrwxrwxrwx 1 root root 27 Jan  3  2018 /var/lib/systemd/timesync -> ../
private/systemd/timesync/

root at mmm /h/pat# ls -la /var/lib/private/systemd/
insgesamt 12
drwxr-xr-x 3 root             root             4096 Jan  3  2018 ./
drwx------ 3 root             root             4096 Jan  3  2018 ../
drwxr-xr-x 2 systemd-timesync systemd-timesync 4096 Okt 19  2017 timesync/

> This will only be a problem for users of unstable/testing, not for users
> who upgrade from stretch → buster directly, as timesyncd in stretch does
> not use DynamicUser=true.
> 
> That said, we should probably add some cleanup routines to remove
> /var/lib/systemd/timesync and
> /var/lib/private/systemd/timesync
> and let the directories be recreated
> 
> Checking the other services, for which DynamicUser=true was dropped,
> like systemd-resolved, they don't appear to be affected afaics as they
> don't use StateDirectory.
This sounds all very plausible and is in line with my understanding, i.e. an 
rm is all which is needed. I just tested it and /var/lib/systemd/timesync is 
really recreated with the correct permissions after deletion when starting 
timesyncd.

Kind regards and thanks
Patrick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190104/836922a1/attachment-0001.sig>