Re: Bizarre date....

From: Bill Marcum (bmarcum_at_iglou.com)
Date: 09/30/05


Date: Fri, 30 Sep 2005 00:56:55 -0400

On Thu, 29 Sep 2005 20:13:46 -0700, Captain Dondo
  <yan@NsOeSiPnAeMr.com> wrote:
> I am having a weird issue on my TS-7000 (arm9) board. It's running Debian
> sarge. When I set the date with ntpdate or ntpd, it is set to Sep. 11
> 1937.....
>
What happens when you set the date with date or hwclock? Have you tried
"ntpdate -d" or "ntpdate -q"?

-- 
Never try to outstubborn a cat.
		-- Lazarus Long, "Time Enough for Love"


Relevant Pages

  • Bizarre date....
    ... It's running Debian ... sarge. ... When I set the date with ntpdate or ntpd, it is set to Sep. 11 ...
    (comp.os.linux.networking)
  • Re: Bizarre date....
    ... >sarge. ... When I set the date with ntpdate or ntpd, it is set to Sep. 11 ... No kidding. ...
    (comp.os.linux.networking)
  • Re: "ntpd -q" is slow compared to ntpdate
    ... Mohit> continue to use ntpdate or sntp to set the time in a one-shot way ... Mohit> before actually running ntpd. ... replacement for 'ntpdate'. ...
    (comp.protocols.time.ntp)
  • Re: ntpd -gq VS ntpdate -B
    ... is normally recommended for a boot sequence prior to starting ntpd. ... "ntpdate -B" slews the time, ... if the difference is more the clock will be ... If the error is less than 0.5 seconds, it will slew the time ...
    (comp.protocols.time.ntp)
  • Re: ntpd -gq VS ntpdate -B
    ... Ntpd -qg with this time difference has the same behavior. ... See following reference of ntpdate manual: ... If ntpdate determines the clock is in error more than 0.5 second ... the servers you have chosen to use. ...
    (comp.protocols.time.ntp)