Am 04.01.19 um 21:49 schrieb Patrick Häcker:
> I think the state to see the problem is quite reproducible: First install
> systemd 239 and afterwards install systemd 240, i.e. I can recreate whatever
> state you need.
It is indeed reproducible easily, which is why I raised this upstream
https:/
Am Freitag, 4. Januar 2019, 12:22:46 CET schrieb Michael Biebl:
> Am 04.01.19 um 11:48 schrieb Patrick Häcker:
> > Hello,
> >
> >> Can you post the output of
> >> ls -ld /var/lib/systemd/timesync
> >> ls -la /var/lib/private/systemd/
> >
> > root@mmm /h/pat# ls -ld /var/lib/systemd/timesync
> > l
Am 04.01.19 um 12:22 schrieb Michael Biebl:
> For completeness sake, can you also post the output of
> stat /var/lib/systemd/timesync/clock
Make that
stat /var/lib/private/systemd/timesync/clock
(I missed that you already deleted /var/lib/systemd/timesync/)
--
Why is it that all of the instru
Am 04.01.19 um 11:48 schrieb Patrick Häcker:
> Hello,
>
>> Can you post the output of
>> ls -ld /var/lib/systemd/timesync
>> ls -la /var/lib/private/systemd/
>
> root@mmm /h/pat# ls -ld /var/lib/systemd/timesync
> lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../
> private/
Hello,
> Can you post the output of
> ls -ld /var/lib/systemd/timesync
> ls -la /var/lib/private/systemd/
root@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@mmm /h/pat# ls -la /var/lib/private/
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
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
This was reverted upstream in
https://github.com/system
Hi,
the problem seems to be mixing two approaches in an incompatible way:
1) /var/lib/systemd/timesync can either be a directory (a) or a symlink to
/var/lib/private/systemd/timesync (b)
2) systemd-timesyncd.service may either contain DynamicUser=yes (a) or not
(b).
1a together with 2b should
Package: systemd
Version: 240-2
Severity: normal
Dear Maintainer,
after updating systemd from 239-15 to 240-2 timesyncd stopped touching
/var/lib/private/systemd/timesync/clock any more and its time stamps
stay at the time of the package upgrade.
Additionally the file is no longer used to update
9 matches
Mail list logo
