Le 29/01/2020 à 11:58, Rainer Weikusat via Dng a écrit :
Dimitris via Dng writes:
On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
run ntpdate from
i've witnessed cases in the past where ntpd wasn't time-syncing
correctly, and ntpdate saved the date/time.
so, IMHO, there's nothing wrong
Anno domini 2020 Wed, 29 Jan 12:46:35 -0500
Steve Litt scripsit:
> On Wed, 29 Jan 2020 10:58:57 +
> Rainer Weikusat via Dng wrote:
>
> > Dimitris via Dng writes:
> > > On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
> > >> run ntpdate from
> > >
> > > i've witnessed cases in the
On Wed, 29 Jan 2020 10:58:57 +
Rainer Weikusat via Dng wrote:
> Dimitris via Dng writes:
> > On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
> >> run ntpdate from
> >
> > i've witnessed cases in the past where ntpd wasn't time-syncing
> > correctly, and ntpdate saved the date/time.
>
Dimitris via Dng writes:
> On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
>> run ntpdate from
>
> i've witnessed cases in the past where ntpd wasn't time-syncing
> correctly, and ntpdate saved the date/time.
> so, IMHO, there's nothing wrong with ntpdate.
There's nothing wrong with ntpdate
On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
> run ntpdate from
i've witnessed cases in the past where ntpd wasn't time-syncing
correctly, and ntpdate saved the date/time.
so, IMHO, there's nothing wrong with ntpdate.
just 2c,
d.
signature.asc
Description: OpenPGP digital signature
On Tue, 28 Jan 2020 16:46:56 +
Rainer Weikusat via Dng wrote:
> some people are passionately convinced that non-local time is a
> misfeature
*glares at satellites*
;)
___
Dng mailing list
Dng@lists.dyne.org
"Dr. Nikolaus Klepp" writes:
> Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not
> into machining will most likely not see the fun part of it, but anyway
> :)
>
> https://www.youtube.com/watch?v=RDKaFJmB254
Not particularly funny --- the systemd timesync service is a C
Quoting Andreas Messer (a...@bastelmap.de):
> This problem has no relation to the existence of a hardware RTC or not.
> On Linux, the hardware RTC is in almost any case only read when the system
> boots/resumes and updated on system shutdown/sleep. During operation,
> Linux always uses a
On Mon, Jan 27, 2020 at 04:17:20PM -0800, Rick Moen wrote:
> Quoting Dr. Nikolaus Klepp (dr.kl...@gmx.at):
>
> > Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not
> > into machining will most likely not see the fun part of it, but anyway
> > :)
> >
> >
On 1/27/20 4:17 PM, Rick Moen wrote:
Quoting Dr. Nikolaus Klepp (dr.kl...@gmx.at):
Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not
into machining will most likely not see the fun part of it, but anyway
:)
https://www.youtube.com/watch?v=RDKaFJmB254
Nik --
Thank you for
Quoting Dr. Nikolaus Klepp (dr.kl...@gmx.at):
> Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not
> into machining will most likely not see the fun part of it, but anyway
> :)
>
> https://www.youtube.com/watch?v=RDKaFJmB254
Nik --
Thank you for the link. I think it should
I've got around 80 servers running Ubuntu 16.04 and 18.04. I noticed the
time was yet again screwed up on them a few weeks ago. Not sure when it
started happening but would guess it was the last systemd update on
12/2019. All hosts are all running timesyncd (after trying to get Chrony
and NTP
Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not into
machining will most likely not see the fun part of it, but anyway :)
https://www.youtube.com/watch?v=RDKaFJmB254
Nik
--
Please do not email me anything that you are not comfortable also sharing with
the NSA, CIA ...
13 matches
Mail list logo
