On Thu, 2023-05-18 at 10:20 -0400, Dan Ritter wrote: > Default User wrote: > > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > > > On Wed, 17 May 2023 12:48:28 -0400 > > > Dan Ritter <d...@randomstring.org> wrote: > > > > > > > Assuming you have network access close to boot time, you might > > > > want to run an NTP daemon to get the time from a selection of > > > > other servers. > > > > > > Concur. > > > > > > > > > > > Debian runs a pool, which is configured by default in ntp- > > > > server > > > > and chrony, at least. > > > > > > Also systemd-timesyncd, which is probably the easiest of these > > > three > > > to > > > set up. > > > > > > > > > > > > If I am running systemd-timesyncd on a single-user, internet- > > connected > > computer, not needing to serve time signals to any other device, > > would > > there be any reason to use ntp instead? > > systemd-timesyncd, ntp-server and chrony are all supposed to > speak the NTP protocol. Nothing, to a first approximation, uses > any other protocol to set time reliably for the system as a > whole. > > -dsr-
Okay, thanks!
