SVN commit showing different time after DSL time change

[Chamara Gunaratne <ch...@focusinc.com>]

Hello,

We have a svn server that is mainly accessed using the subclipse Eclipse svn
plugin.  After Sunday's time change, commits to svn are time stamped with a
time one hour in the future, i.e a commit done at 11:10 am is time stamped
12:10 pm.  Svn is accessed using svn+ssh and the Linux server (kernel
2.6.5-7.276) running svn has the correct time and all the clients accessing
svn have the correct time too.  

 

We started to notice this yesterday, and so far haven't been able to find a
solution. Any help is greatly appreciated :-) Thanks!

 

Chamara

RE: SVN commit showing different time after DSL time change

[Chamara Gunaratne <ch...@focusinc.com>]

Gavin,

Thanks for your reply. The problem turned out to be a corrupted/outdated
time zone file. Updating the server with the latest time zone information
did the trick.

Cheers,

 

Chamara

 

From: Gavin 'Beau' Baumanis [mailto:gavin@thespidernet.com] 
Sent: Tuesday, March 11, 2008 8:22 PM
To: Chamara Gunaratne
Cc: users@subversion.tigris.org
Subject: Re: SVN commit showing different time after DSL time change

 

Hi,
I don't pretend to have the naswer for you,
But we did have a very similar issue on one of our servers - where the JAVA
installed on th server did not have correct region / timezone settings.
This effected several "other" systems that I would have thouhgt impossible
to be influenced by the JAVA settings. - but none the less correcting the
JAVA install/config corrected all datetime issues we were having.

-Gavin.

Chamara Gunaratne wrote: 

Hello,

We have a svn server that is mainly accessed using the subclipse Eclipse svn
plugin.  After Sunday's time change, commits to svn are time stamped with a
time one hour in the future, i.e a commit done at 11:10 am is time stamped
12:10 pm.  Svn is accessed using svn+ssh and the Linux server (kernel
2.6.5-7.276) running svn has the correct time and all the clients accessing
svn have the correct time too.  

 

We started to notice this yesterday, and so far haven't been able to find a
solution. Any help is greatly appreciated :-) Thanks!

 

Chamara



__________ NOD32 2940 (20080312) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

Re: SVN commit showing different time after DSL time change

[Gavin 'Beau' Baumanis <ga...@thespidernet.com>]

Hi,
I don't pretend to have the naswer for you,
But we did have a very similar issue on one of our servers - where the 
JAVA installed on th server did not have correct region / timezone settings.
This effected several "other" systems that I would have thouhgt 
impossible to be influenced by the JAVA settings. - but none the less 
correcting the JAVA install/config corrected all datetime issues we were 
having.

-Gavin.

Chamara Gunaratne wrote:
>
> Hello,
>
> We have a svn server that is mainly accessed using the subclipse 
> Eclipse svn plugin.  After Sunday's time change, commits to svn are 
> time stamped with a time one hour in the future, i.e a commit done at 
> 11:10 am is time stamped 12:10 pm.  Svn is accessed using svn+ssh and 
> the Linux server (kernel 2.6.5-7.276) running svn has the correct time 
> and all the clients accessing svn have the correct time too.  
>
>  
>
> We started to notice this yesterday, and so far haven't been able to 
> find a solution. Any help is greatly appreciated :-) Thanks!
>
>  
>
> Chamara
>

Re: SVN commit showing different time after DSL time change

[Matthew Pounsett <ma...@conundrum.com>]

On 11-Mar-2008, at 11:32 , Chamara Gunaratne wrote:

> Hello,
> We have a svn server that is mainly accessed using the subclipse  
> Eclipse svn plugin.  After Sunday’s time change, commits to svn are  
> time stamped with a time one hour in the future, i.e a commit done  
> at 11:10 am is time stamped 12:10 pm.  Svn is accessed using svn+ssh  
> and the Linux server (kernel 2.6.5-7.276) running svn has the  
> correct time and all the clients accessing svn have the correct time  
> too.

Hrm.. I haven't seen this, running a very similar setup.  The time  
stamps in in all of our commits are correct.

Assuming your tzdata package is up to date, then I suppose it's  
possible Apache has cached old time zone data.  Have you tried  
restarting the httpd?