[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 2 users working on same file caused a change to be reverted rather than merged

From: Jan Hendrik <list.jan.hendrik_at_gmail.com>
Date: Mon, 16 Feb 2009 11:49:23 +0100

Concerning Re: 2 users working on same file ca
Andreas Schweigstill wrote on 16 Feb 2009, 9:03, at least in part:

> Yes, and some years ago I found out that on network shares some
> applications create timestamps based on the client's system clock and
> some on the server's. :-/ It took me several hours to figure this out
> because in most cases our production process worked properly and in
> some cases the dependencies weren't resolved properly. The behaviour
> depended on weather it was a native Windows/OS/2 application or an old
> MS-DOS application.
> In mixed environments there can also occur some file synchronisation
> problems regarding to NFS and Samba, especially on older NFS server
> implementations.

This reminds me of an issue we have with an only occasionally
used Buffalo Linkstation (NAS) running some embedded Linux with
Samba. When syncing files to it quite often it would set its own
current time on the synced files, but not regularly, and probably not
even on all files during one and the same operation. For syncing
always the same Windows application (Total Commander) is used.
 It might have something to do with how much local time deviates
from NAS time, but I never investigated that. Funny thing though: it
only happens when the files already exist on the Linkstation, any
"new" file invariably gets the timestamp it has on the local machine.

Jan Hendrik

Freedom quote:

     Facts do not cease to exist because they are ignored.
               -- Aldous Huxley


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-16 11:54:33 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.