On 1/31/24 13:19, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
# Stop bad estimates upsetting machine clock.
maxupdateskew 100000.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can’t be used along with the 'rtcfile'
directive.
rtcsync
I'll comment that line
# Step the system clock instead of slewing it if the adjustment is larger
than
# one second, but only in the first three clock updates.
makestep 1 3000
I had tried 30, and it did it about that many time ack the tcpdump log
I'm tracking. And I'll put the 300 back in, that ack the tcpdump
monitor seemed to effective. but I've not found in the docs, anything
that will modify how far the step will change it, The first arg is one
second.
chrony seems to be the fave method for the arm64's but I have had
better luck using ntpsec without the security on all other wintel
machines. Its ntpsec I'm using on this machine to be a stratum 2 server
for the rest of my local net. So that's what all the other local
machines see. timedatectl bombs when asked to set-time, regardless of
how many space separated arguments is says too many arguments. Aha! the
time argument needs single quotes around it! The help screen is wrong
but the man page says " ". So I have it now set for about 4 hours ago.
Now about 5 seconds off, but its not querying my server. More man page
perusal. I am getting the impression that timedatctl ultimately uses he
first time service it can find, and while I have the clock sey pretty
close, it nat offer ntp until there is an available ntp client, and I
used apt to purge both chrony and ntpsec. So I;ll reinstall ntpsec. Done
Then I went clear around the mulberry tree and copied (because my sshnet
mounts of all these machine is as a user) the
/sshnet/go704/etc/ntpsec/ntp.conf to my home dir on that box, then fired
up a user mc and copied that file from /sshnet/go704/home/gene to
/sshnet/bpi51/home/gene.
went to a different workspace, fired up a sudo mc, copied that file to
that machines /etc/ntpsec dir, then fixed the perms back to 0600.
Then restarted ntpsec by stopping it, then starting it again so it would
read the new file. Then:
gene@bpi51e5p:~$ timedatectl status
Local time: Wed 2024-01-31 15:40:13 EST
Universal time: Wed 2024-01-31 20:40:13 UTC
RTC time: Wed 2024-01-31 20:40:13
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
NTP service: n/a
RTC in local TZ: no
And my tcpdump trace here?:
15:51:01.235371 IP bpi51e5p.coyote.den.ntp > coyote.coyote.den.ntp:
NTPv4, Client, length 48
15:51:01.235523 IP coyote.coyote.den.ntp > bpi51e5p.coyote.den.ntp:
NTPv4, Server, length 48
15:52:06.236633 IP bpi51e5p.coyote.den.ntp > coyote.coyote.den.ntp:
NTPv4, Client, length 48
15:52:06.236701 IP coyote.coyote.den.ntp > bpi51e5p.coyote.den.ntp:
NTPv4, Server, length 48
IOW, its working. And I found another off by about an hour, so I copied
that same file it it, problem solved.
Now, I still have more cats to skin but solving those two problems will
help. Now I can get back to the real problem. Lack of docs to make a
TMC-2209, a very common motor driver in the stepstick category, work in
the uart interface mode in a BTT octopus Pro controller cards driver
sockets 2, 3 & 4. Add about 12 jumpers and put them back in
step/dir/enable mode is the next test. That's going to take some coffee
I haven't made yet today.
Thanks for the nudge to make me think, Greg, take care & stay well.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
