>
> > [1]: https://wiki.ubuntu.com/Netplan#Frequently-asked_questions
>
> Sorry, I completely dropped the ball on this.
>
No problem at all, I know there is always one task too mcuh :-)
> I have again looked through all the open bugs and I've come to the
> conclusion that ntpdate in it's current
Hi Christian,
>> I'm therefor proposing a complete rewrite
>>
>> - new package sntp-hooks
>> - depends on sntp, ships hooks for ifupdown and possibly others (like
>> NetworkManager or systemd-network or whatever Ubuntu is doing now)
>> - executes the actual sntp synchronisation non-blockin
On Tue, Jan 2, 2018 at 10:22 PM, Bernhard Schmidt wrote:
> On Thu, May 05, 2016 at 01:44:06PM -0500, Christian Ehrhardt wrote:
>
> Hi Christian,
>
> thanks for bringing this up.
>
>> While these days the systemd based timesync* tools are doing most of the
>> work there is still a lot of buzz aroun
On Thu, May 05, 2016 at 01:44:06PM -0500, Christian Ehrhardt wrote:
Hi Christian,
thanks for bringing this up.
> While these days the systemd based timesync* tools are doing most of the
> work there is still a lot of buzz around the automated ntpdate on ifup
> being good/bad for various reasons.
Package: ntp
Version: 1:4.2.8p7+dfsg-3
While these days the systemd based timesync* tools are doing most of the
work there is still a lot of buzz around the automated ntpdate on ifup
being good/bad for various reasons.
I'll try to to summarize the outcome of multiple discussions and bugs
around t
5 matches
Mail list logo