I've installed a new Linux distro on my eee900. Afterwards I noted that time marks in the webmail/calendar application I use at work (Zimbra Collaboration Suite) were 4 hrs off if I chose the "Advanced (AJAX)" interface (works OK in the "Standard (HTML)" interface.

System clock was set to GMT+2 which is correct (CET summer time). The command "clock" in a terminal window also gave the time as GMT+2. But when I typed

javascript:new Date()

in the Firefox address bar the time came up as GMT-2 :confused:

I have 'solved' the problem by setting the system clock to GMT-2 and now the

javascript:new Date()

entry gives me GMT+2 plus that time marks in Zimbra are correct.

I've tried both Local and UTC time settings (and made a timeconfig setup accordingly), but no change.

Even if my 'solution' works, it's a bit frustrating not to understand what's going on and why I get two different time settings. It's as if the time/date setting application works backwards but that's probably a too simple explanation

EDIT: Solved - I made a new attempt with the timeconfig command. With localtime chosen the timezone setting given by hwclock now is CEST instead of GMT+2, the setting given by javascript:new Date() is GMT+2, Zimbra marks shows up correct. Don't know why I didn't succeeded earlier :P

Edited 8 August, 200916 yr by swedishskoda
problem solved

Thanks, I'll try to memorise that for the future Linux is wonderfully simple if you only know what to put in the terminal... must admit that I'm still under MS influence and prefer user-friendly GUIs but trying hard to better myself

Thanks, I'll try to memorise that for the future Linux is wonderfully simple if you only know what to put in the terminal... must admit that I'm still under MS influence and prefer user-friendly GUIs but trying hard to better myself

I ended up trying to configure a wireless network card on Ubuntu server i.e. without a gui at all. That was fun... Taught me a lot though.

Another thing to watch is that if you dual boot Linux usually expects BIOS time to be in UTC then adds to it while windows expects BIOS time to be in local time.

That one has confused many people