Every time I reboot my Raq, the date is changed to something completely wrong like 2004 or 2007

even though I change the date using something like

date 0713141403

and then

hwclock --systohc

the clock is reset to that absurd 2004 or 2007 date ...

any clues anyone ? thanks !

In the GUI, under Control Panel, Date/Time, do you have an NTP server filled in there?

no I don't have an NTP ... is that needed ?

search google for NTP servers, then put one in there

ok but from what I understand this will "only" set the date accordingly to the date given by that NTP server ...

why is my webserver losing his date ?

No clue,
perhaps a bad/empty CMOS battery?

yeah I was thinking the same but then why not back to 1970 or 1980 instead of 2004 ? :confused:

I don't know how to do this on a RAQ (I guess there should be some kinda binary package or something like that)

put it in the init scripts and voilà

as for answering why it's happening... I wouldn't put my mind into it, it's worthless taking on account that you could (with ntp) set your time based on servers which consequently sets its clock with an array of atomic clocks

ntp deals with delay times and such issues so it's virtually exact world time

Raqs (3,4,XTR,550's) already have ntp installed. You can either configure via the control panel or configure via the ntp.conf file.


A list of time servers is here:
http://www.eecis.udel.edu/~mills/ntp/servers.htm

Also, you hardware (bios) clock could be wrong so that during each reboot it gets reset. Set you clock first and then reset your hardware clock.

Also, if you are running a firewall you will need to modify your ruleset to allow the timeserver responses into your server. By default the UPD protocol is used on ports 123.

For more info on time issues on servers see:
http://www.linuxsa.org.au/tips/time.html