If you want to get an answer I urge you to also contact the submitter
(me) by either by ccing me directly or by ccing [EMAIL PROTECTED]
Otherwise it is very unlikely that I eventually catch your comment. See
#351856.
> Given that the whole setup works like a charm for me I think the severity is
> too high, thus I downgraded it. From looking at /etc/ppp/ip-up.d/chrony I'd
I had to downgrade, because chrony also broke suspend2disk[1], so I
could as well have tagged it critical because it affects other
applications as well. Still I have to admit that this version also runs
on my sid/amd64 machine and works well there.
> guess that $PASSWORD is empty for you. Could you please verify?
It is not empty. And if it was empty, downgrading would not solve the
issue.
Any other suggestions?
Helmut
[1] I use hibernate and restart chrony on wakeup to synchronize with
new servers. As chrony does not terminate, hibernate doesn't either
and as long as hibernate runs, it will not hibernate again. So
hibernate got borked, too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
