We hit this a number of times with svn+ssh until we got everyone to
properly set their umask. haven't had it happen since then, however.
-Brian
On Jun 11, 2004, at 2:15 PM, Stefano Mazzocchi wrote:
Pier Fumagalli wrote:
On 11 Jun 2004, at 22:02, Jim Moore wrote:
Actually, the "all or nothing" part of the transaction isn't a big
deal
because, as you said, it's very rare that a commit in CVS would fail.
Problem being (though) is that I've seen Subversion (1.0.2 under
Linux) fail right because of that... Somehow an "atomic" transaction
was left open on the server, don't ask me why...
Basically, after that commit failed, the entire repository was so
slow that most TCP/IP connections were failing after 3 minutes for
timeouts...
Only solution was to run a "svn recover" followed by a "svn rmtxt"
and again followed by another "svn recover"...
I am experiencing random svn corruptions with svnserve over ssh with
svn 1.0 (how do I find out the real version btw? why isn't svn
-v|--version give me the version?) over linux 2.6.4
any clue?
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
