On 11/25/2014 03:28 PM, Robert Moskowitz wrote:
My cubieboards do not have a battery backing up the clock, so every boot
comes up with the date:
Jan 1 00:
But ntpd to the rescure to set the date. However, it seems the slew has
gotten too great:
Jan 1 00:01:33 medon ntpd[765]: 0.0.0.0 0617 07 panic_stop +154604256
s; set clock manually within 1000 s.
and now nptd is not running. I did set the date with 'date
MMddhhmmyyyy', but still need to restart ntpd.
It would seem to me that a hack around this is to run date in the boot
process. Something like:
date 010101012014
Just before starting of ntpd. But I know nothing of boot scripts, where
to put this command, and if that would be the proper format within the
boot process.
Can anyone lend me a hand on what/where to set this up?
I would have thought the correct way to deal with this would be to use
the ntpdate service in addition to the ntpd service. First ntpdate sets
the clock as a one off, then ntpd keeps it in sync periodically.
The only problem I foresee is that fsck may insist on running every time
because the last mount time will be in the future on every boot.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
