On Mon, Mar 13, 2023 at 08:04:53AM -0400, Todd Gruhn wrote:
> Because our time (in spring) changed from 6:00am ---> 7:00am.
No need to do anything, if you have set the correct timezone it
should adjust for DST automatically.
> I was hoping NetBSD would just take to a server to get latest time,
HMMM
timed found in Evi Nemeth's book ...
On Mon, Mar 13, 2023 at 8:04 AM Todd Gruhn wrote:
>
> Because our time (in spring) changed from 6:00am ---> 7:00am.
>
> I remember doing this by using 'date'.
>
> I was hoping NetBSD would just take to a server to get latest time, then set
> NetBSD
Because our time (in spring) changed from 6:00am ---> 7:00am.
I remember doing this by using 'date'.
I was hoping NetBSD would just take to a server to get latest time, then set
NetBSD time with this. (from Washington D.C. Naval server)
On Mon, Mar 13, 2023 at 5:50 AM Riccardo Mottola
Hi,
Todd Gruhn wrote:
Last night I set clock 1hr ahead.
how did you set it ahead?
Today, X-clock still says time is 4:20pm (it should be 5:20pm).
did you reboot/restart in the meanwhile?
Why isnt this being set/changed? Must I use 'date' ???
what does "date" say in the console?
The
Last night I set clock 1hr ahead.
Today, X-clock still says time is 4:20pm (it should be 5:20pm).
Why isnt this being set/changed? Must I use 'date' ???
