INTL 3:770/1 3:770/3   
   REPLYADDR tnp@invalid.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  77f1c123   
   REPLY:  9c0a1398   
   PID: SoupGate-Win32 v1.05   
   On 09/04/2024 23:32, Knute Johnson wrote:   
   > On 4/9/24 15:47, druck wrote:   
   >> On 09/04/2024 17:00, The Natural Philosopher wrote:   
   >>> RPI 4B.   
   >>> Rebooted. Clock wrong.   
   >>> 1hr later, clock still wrong?   
   >>   
   >> Probably due to using systemd-timesyncd which I've never seen actuall   
   >> working. Install the ntp service and it will work.   
   >>   
   >> It's one of the many parts of Bookworm I've had to junk and restore   
   >> the way I did things in Bullseye.   
   >>   
   >> ---druck   
   >>   
   >   
   > timesyncd works fine.   
      
   No, it does not   
      
   > Make sure that the route to the internet isn't   
   > blocked.   
      
   Its fine   
      
      
     Use the command timedatectl show-timesync --all to see where   
   > timesyncd is looking for time.   
      
   LinkNTPServers=   
   SystemNTPServers=   
   RuntimeNTPServers=   
   FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org   
   2.debian.pool.ntp.org 3.debian.pool.ntp.org   
   ServerName=0.debian.pool.ntp.org   
   ServerAddress=51.89.151.183   
   RootDistanceMaxUSec=5s   
   PollIntervalMinUSec=32s   
   PollIntervalMaxUSec=34min 8s   
   PollIntervalUSec=34min 8s   
   NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-25,   
   RootDelay=3.021ms, RootDispersion=106us, Reference=55C7D665,   
   OriginateTimestamp=Wed 2024-04-10 10:01:40 BST, ReceiveTimestamp=Wed   
   2024-04-10 10:01:40 BST, TransmitTimestamp=Wed 2024-04-10 10:01:40 BST,   
   DestinationTimestamp=Wed 2024-04-10 10:01:40 BST, Ignored=no,   
   PacketCount=36, Jitter=684us }   
   Frequency=-804732   
      
     You can always specify NTP servers in   
   > /etc/systemd/timesyncd.conf.   
      
   I basically uncommented everything that was commented out   
      
      
   Use timedatectl status to see what it is   
   > doing.   
   >   
   timedatectl status   
                   Local time: Wed 2024-04-10 10:29:13 BST   
               Universal time: Wed 2024-04-10 09:29:13 UTC   
                     RTC time: n/a   
                    Time zone: Europe/London (BST, +0100)   
   System clock synchronized: yes   
                  NTP service: active   
              RTC in local TZ: no   
      
   In order to get this far I had to edit that file and I disabled wlan0 on   
   the Pi 4.   
   At some point it started working but doesn't seem to be *regularly*   
   contacting anything last entry from   
      
   $systemctl status systemd-timesyncd.service   
      
   Apr 09 21:30:38 Coriolanus systemd-timesyncd[547]: Contacted time server   
   51.89.151.183:123 (0.debian.pool.ntp.org)   
      
      
   --   
        “I know that most men, including those at ease with problems of the   
   greatest complexity, can seldom accept even the simplest and most   
   obvious truth if it be such as would oblige them to admit the falsity of   
   conclusions which they have delighted in explaining to colleagues, which   
   they have proudly taught to others, and which they have woven, thread by   
   thread, into the fabric of their lives.”   
      
        ― Leo Tolstoy   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/220   
   SEEN-BY: 135/225 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1   
   SEEN-BY: 221/6 360 226/17 30 100 227/114 229/110 111 112 113 200 206   
   SEEN-BY: 229/307 317 400 426 428 470 550 616 664 700 240/1120 266/512   
   SEEN-BY: 267/800 282/1038 291/111 292/854 301/1 113 812 310/31 320/219   
   SEEN-BY: 322/757 335/364 341/66 342/200 396/45 460/58 633/280 712/848   
   SEEN-BY: 770/1 3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426