I'm really happy with my Pi so far, but now that the website I'm developing on it is starting to need the time and date, I thought it was about time to get NTPd working. So I installed an NTP server onto my Windows machine which acutally has a clock in it, and I got my network switch (which doesn't have an RTC) to successfully update its software clock to this Windows NTPd. Then I try and get the Pi to update... Not so successful:
[root@raspberry ~]# ntpd -ds
listening on 127.0.0.1
ntp engine ready
reply from 192.168.0.2: not synced, next query 655s
^Cntp engine exiting
dispatch_imsg in main: pipe closed
Lost child: child exited
Terminating
[root@raspberry ~]# date
Fri Jan 2 04:01:00 BST 1970
[root@raspberry ~]#
So it says that my 192.168.0.2 (my windows box) isn't synced. Can I tell it to ignore this like my network switch must? Why doesn't it update the time?
Note: I can't get the Raspberry Pi to update directly from the internet due to the way my network's set up.
Thanks for any guidance..
-g
argument to allow you to jump the clock. Or see if the ntpdate command is available. Note that normally you'd want to run ntpd as a daemon. – nos Nov 4 '12 at 10:47