Am 04.01.19 um 10:23 schrieb Michael Biebl: > Hello, > > systemd-timesyncd.service in previous releases used DynamicUser=true. > This will create a symlink /var/lib/systemd/timesync pointing at > ../private/systemd/timesync and make sure it is properly owned by > systemd-timesync:systemd-timesync
Actually, it's the combination of StateDirectory=systemd/timesync + DynamicUser=true which creates /var/lib/systemd/timesync as symlink to ../private/systemd. 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. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
