Michiel:

Thanks for filing that bug-report. You saved my brain 

ikarus

to johnh3 :

Yes, many thanks for that and I agree there is something wrong about the way we cannot control the clock settings either as user or root.

However, I think maybe the timezone-data is yet another separate issue to follow up

*********************************************************************************************************

to Michiel :

I completely agree with your final comment.

I went ahead with installing the pytz software and it installed correctly. I thought that maybe the OS would pick up on this and use the new data automatically. However its no go - the time remains an hour fast for poor little Mauritius!

So, now I'm not sure if its the 2009n data that's wrong  or whether pytz itself is mis-managing it. It all looks awafully complicated and well beyond my comprehension!   

I guess, as you say, a bug report is in order here. Now I'll try to work out how to do that.   


ikarus

hi Michiel

Thanks for your response - I shall have a look at the rdate packeage.

Regarding DST in Mauritius - this was a one year trial and was discontinued from this year. Ubuntu's tzdata appears to have it correct.

NTP time servers, as I understand it, do not broadcast local time to anywhere. I believe the data they send is in fact "UNIX EPOCH" time which is referenced to a time/date which commenced in 1970 or thereabouts. So it is purely a number which increments and is the same anywhere in the world at any particular moment in time.  The time-clock software running in the OS converts this number to a recognisable format  taking into account the user's (stated) location.

Having said that, my latest simple work-around is to change my local time zone to "Dubai" . They've got my time over there 

Best regards

ikarus

PS I believe that the UNIX EPOCH system actually runs out some time around two thousand and thirty something, due to the counter reaching overflow. I don't know what they plan to do about this but I expect I'll be long gone before then !!! 

Hello bubbel

Thanks for your reply.

I have the system set to automatic as you suggest. The clock is still one hour fast. I think the time-zone data for Mauritius is wrong in Pardus. We do not have DST here this year.

Why will the system not let me set the time manually? I do not want to do this but it would be ok for a quick work-around.

Best regards

ikarus

The time as shown by the on-screen clock is always one hour fast. When I go to clock settings and enter my root password I can change the system to manual and correct the reading but after a couple of seconds it changes back to being an hour fast.

Even when I resort to CLI and use ntpdate it shows up as an hour fast. I think the time zone information may be wrong but I don't know how to access this.

My timezone is INDIAN/MAURITIUS which was using daylight saving time last year but not currently.

Ikarus