Your message dated Sat, 5 May 2018 03:15:49 +0200
with message-id <[email protected]>
and subject line Re: Bug#895821: 873185 made which time service starts
unreliable
has caused the Debian Bug report #895821,
regarding 873185 made which time service starts unreliable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895821
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 238-4
Hi,
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873185 an old
workaround was dropped because all NTP servers now
ship Conflicts=systemd-timesyncd.service but in my tests I found that
systemd in this case is still unreliable.
We end up with a NTP server (chrony, ntp, ...) and systemd-timesyncd both
being enabled and systemd on startup randomly picking one of them.
I filed systemd upstream https://github.com/systemd/systemd/issues/8730 to
get educated how one could control it or at some time there might be a way
to express this added.
But until then I wonder how we can make any guarantees which service is
started.
OTOH while trivial experiments trigger easily I haven't seen chrony to be
knowcked out by systemd-timesyncd in real-life. Maybe there is a second
safety mechanism I don't know yet?
But if I'm right and this is just as unreliable as it is in my tests I
wonder if we should take the old stop-gap measure back into systemd for now
in Debian and Ubuntu.
Note - LP Bug in ubuntu: https://bugs.launchpad.net/systemd/+bug/1764357
P.S. I was unsure, but think this is not a re-open of the old bug(s). So I
decided for a new report and setting Michael (systemd / old bug) and
Vincent (chrony) on CC.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
On Tue, 17 Apr 2018 17:32:10 +0200 Christian Ehrhardt
<[email protected]> wrote:
> [...]
>
> So, I'm not sure if any changes to the status quo actually improve the
> > current situation, but I'm open to other ideas.
>
>
> Thanks Michael for the reply,
> in the meantime I also found that it seems to be no issue in most real
> world cases - more details on that in the LP bug.
>
> I subscribed to the upstream issue 7104 you pointed me to (thanks) but I
> think for
> this case I reported here we can close it for now and keep the status-quo
> for now.
>
> I might have a small chrony patch to improve how it works together with
> systemd-timesyncd, but that is a totally different issue.
>
> So please feel free to close this bug unless you are interested to keep it
> open for further discussion.
This bug report has been open for a few weeks, but no further discussion
happened. So at this point I'm going to close it.
If better ideas come up how to handle this situation, we can reopen it.
Regards,
Michael
--
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
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
