On Tue, Sep 23, 2008 at 14:42, Ryan Schmidt
<subversion-2008c_at_ryandesign.com> wrote:
> On Sep 23, 2008, at 12:39 PM, Brandon Humphrey wrote:
>
>> I have recently noticed that the system time on our Subversion server is a
>> few minutes off (~3 minutes fast). I'd like to fix the time by syncing with
>> an internal date server, and configuring ntpd to keep it in sync.
>>
>
> Excellent idea!
>
>> We are running Subversion 1.4.3 on Slackware 11.
>>
>>
>> Is there anything I need to be concerned with when performing the initial
>> sync?
>>
>
> If anybody commits new revisions in the ~3 minutes after you sync, the
> revisions will appear to be chronologically out of order, which will make
> the "-r{date}" revision syntax not work. You can either do your time sync at
> a time when nobody will be committing, or tell people not to commit until
> the clock catches up to where it was, or retroactively fix the revisions'
> dates so they're still chronological (svn propedit --revprop -r 123
> svn:date). Or, if you never use the "-r{date}" syntax then you don't need to
> worry about it at all.
Or shut down your SVN server process (Apache or svnserve) for about 5
minutes while you do the sync and then wait for the world to catch up
to the time the server used to think it was.
I tend to find that when I tell people "don't do X during this time
period" they all do it before the time is up because they want to test
the system. Shut down the server and that's impossible.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-23 20:52:38 CEST