Sorry, I stopped using chrony some time ago and the laptop that was
generating this bug was murdered by a cup of tea.
On Sat, Oct 5, 2019 at 02:43, Michael Biebl wrote:
Seems like Conflicts= do not work reliably to ensure the
systemd-timesyncd.service is not started during boot.
See also the
Seems like Conflicts= do not work reliably to ensure the
systemd-timesyncd.service is not started during boot.
See also the upstream bug report
https://github.com/systemd/systemd/issues/7104
We've re-added the Conditions to systemd-timesyncd.service.
#
/lib/systemd/system/systemd-timesyncd.servic
On Sun, 7 Jan 2018 17:53:29 +0100 Vincent Blut wrote:
>
> After reading the bug report again, I notice that I did not ask you to
> disable systemd-timesyncd. So could you please run “systemctl disable
> systemd-timesyncd” and report chronyd’s status after rebooting?
FWIW, I had the same problem (
Hi Andres,
On Wed, Dec 27, 2017 at 02:54:46PM +0100, Vincent Blut wrote:
Hi Andres,
On Mon, Dec 18, 2017 at 03:14:22PM -0800, Andres Salomon wrote:
On Tue, 12 Dec 2017 01:46:08 +0100
Vincent Blut wrote:
Hi Andres,
First of all, I would like to apologize for not having answered
earlier, but
Hi Andres,
On Mon, Dec 18, 2017 at 03:14:22PM -0800, Andres Salomon wrote:
On Tue, 12 Dec 2017 01:46:08 +0100
Vincent Blut wrote:
Hi Andres,
First of all, I would like to apologize for not having answered
earlier, but I’m very busy these days.
No worries. At this point, should we enlist h
On Tue, 12 Dec 2017 01:46:08 +0100
Vincent Blut wrote:
> Hi Andres,
>
> First of all, I would like to apologize for not having answered
> earlier, but I’m very busy these days.
No worries. At this point, should we enlist help upstream? I'm kind
of at a loss for what to do next.
pgpn9VVUlIIM
On Tue, 5 Dec 2017 00:55:43 -0800
Andres Salomon wrote:
> Alright, some progress...
>
> Vincent asked me privately to try switching to sysvinit. When I did
> that, chronyd started successfully on boot. So that narrows it down
> to some kind of systemd interaction problem.
>
> I messed around
Alright, some progress...
Vincent asked me privately to try switching to sysvinit. When I did
that, chronyd started successfully on boot. So that narrows it down to
some kind of systemd interaction problem.
I messed around with the chronyd.service file, and commenting out the
Conflicts line res
[Removing Paul from Cc]
What does “journalctl -u chrony” return when that happens?
dilinger@e7450:~$ sudo journalctl -u chrony
-- No entries --
Not surprising as chrony start-up has been strangely canceled:
Dec 02 09:07:41 e7450 systemd[1]: chrony.service: Job chrony.service/start
finished
Hi,
On Fri, Dec 01, 2017 at 09:17:38PM -0800, Andres Salomon wrote:
On Fri, 1 Dec 2017 21:39:33 +0100
Paul Gevers wrote:
Control: tags -1 moreinfo
I forward the question to the submitter. (@Vincent, in the BTS, the
submitter is not automatically subscribed, so never assume that).
Thanks fo
On Fri, 1 Dec 2017 21:39:33 +0100
Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> I forward the question to the submitter. (@Vincent, in the BTS, the
> submitter is not automatically subscribed, so never assume that).
Thanks for Cc'ing me, Paul!
>
> Andres, is the issue always reproducibl
Control: tags -1 moreinfo
I forward the question to the submitter. (@Vincent, in the BTS, the
submitter is not automatically subscribed, so never assume that).
Andres, is the issue always reproducible?
Paul
On 12/01/17 17:20, Vincent Blut wrote:
> Hi Andres,
>
> On Fri, Dec 01, 2017 at 12:38:
Hi Andres,
On Fri, Dec 01, 2017 at 12:38:26AM -0800, Andres Salomon wrote:
Package: chrony
Version: 3.0-4+deb9u1
I'm running debian stable (stretch). When I do a fresh
install of chrony, for some reason it doesn't start on boot. This is without
touching any of the config files.
Curious, you
Package: chrony
Version: 3.0-4+deb9u1
I'm running debian stable (stretch). When I do a fresh
install of chrony, for some reason it doesn't start on boot. This is without
touching any of the config files.
dilinger@e7450:~$ systemctl is-enabled chrony
enabled
dilinger@e7450:~$ systemctl status c
14 matches
Mail list logo
