Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: ntpdate exited with code 1
-------- Ursprungligt meddelande --------
Den 2025-06-26 17:43, Martin Neitzel <neitzel%hackett.marshlabs.gaertner.de@localhost> skrev:
> > Setting date via ntp.
> > Exiting, name server cannot be used: Temporary failure in name resolution (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary failure in name resolution (2)
> > /etc/rc.d/ntpdate exited with code 1
> > [...]
> >
> > ntp is running by the time I get to X
>
> > Any clues?
>
> So all's well, eventually, and you could ignore the initial problem
> (the Temporary failure).
Thanks, exactly my plan for now.
The only thing is (I've wrote it already) this wasn't happening a month or so ago (don't remember exactly when it started).
[...]
> In that case, setting the time manually (date(1)) will allow you
> to get going.
>
> On amd64 platforms, netbsd should initialize its clock from the
> computer's battery-backed-up real-time-clock. It should be set
> to the proper date & UTC(!) time in the BIOS/UEFI.
Yes, I used to have it like that but, I need to set it up too often (once or twice a month) as the CMOS battery has seen much better days. That's why I started using ntpdate, to avoid the need to dig into the BIOS and adjunkt the clock every other week.
Home |
Main Index |
Thread Index |
Old Index