From: tnp@invalid.invalid   
      
   On 10/04/2024 09:30, Chris Green wrote:   
   > 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.   
   >>   
   > I have bookworm running on two systems, one is a 2Gb Pi 4B and the   
   > other is an ancient Beaglebone Black.  Both show the right time   
   > without any intervention from me.  I checked and the Pi 4B is running   
   > systemd-timesyncd.  ...., and the BBB is also running systemd-timesyncd.   
   >   
   All I know is that I powered the pi4B off for around 15 hours, and when   
   I rebooted it, it had an incorrect clock for at least two hours after   
   reboot.   
      
   That is unacceptable for an 'out of the box' OS install.   
      
     systemd-timesyncd may be fine, but whatever it was supposed to do, it   
   wasn't doing it.   
      
   And none of this is well documented. As someone remarked about CMAKE,   
   "software that cannot be used because *no one knows how it works*, is   
   useless"   
      
      
      
      
      
      
   --   
   "When a true genius appears in the world, you may know him by this sign,   
   that the dunces are all in confederacy against him."   
      
   Jonathan Swift.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)