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

Re: Problem committing new files through apache2 on OS X

From: Aaron Hilton <otri_at_uvic.ca>
Date: 2005-03-12 22:18:21 CET

Just to follow up. I managed to check in the file, but I had to do a
couple of things first.

1) I was forced to convert from BDB into an FSFS repository database.
2) I could then checkout the code tree directly using file:///.../

(... I have a request about svnadmin and svn client at the bottom ...)

I will try to illustrate what else happened in a chronological order:

- To complicate the matters, I had the latest version of Apache2 
compiling in the background... so anyway. I copied the 
InfoPlist.strings file into the directly accessed file:///.../ code 
tree and could finally add and commit the file.
- Around this time Apache2 finished compiling off of Fink, and got 
- I could update and get the new file in my normal svn http://.../ code 
tree without a hitch.
- Now, here's the kicker.  Up to this point, adding huge wads of binary 
data would also cause similar crashes in the svn client as that 
exhibited by InfoPlist.strings file.  But now I added the new binary 
data with no problem. Huzzah!
In conclusion...
I think it was a combination of converting my repository from BDB into 
an FSFS database, and upgrading Apache2.  The SVN client crash was 
probably due to accessing Apache2 and not reacting very nicely to some 
kind of failure on my server.  So, when I upgraded Apache2, it may have 
fixed some concurrency issue.   I'm not sure.
Finally, the BDB archive seems outdated compared to FSFS, and seems to 
be posing a problem for those wanting to checkout directly using the 
file:///.../ protocol.
   Could we have svnadmin default to creating an FSFS repository instead 
of a BDB repository?
   Also, could we have SVN client handle some signals like SIGINT for 
Ctrl-C abort, or SIGTERM for kill to work correctly?  Having to fire up 
another terminal, kill -9 the svn client, then running svn cleanup is 
time consuming and more likely to cause problems in this case of 
failure.  Also, would it be possible to have svn run some kind of 
timeout handler for internet communications so it doesn't hang 
indefinitely, even when the socket is long gone?
- Aaron.
On 2-Mar-05, at 1:54 AM, Aaron Hilton wrote:
> Hi Stephen,
> The adding worked fine. SVN marked the .strings file correctly as 
> binary when added (iirc).
>  Just the commit afterwards hangs. That's when it tries to transmit 
> the file to the WebDAV repository.
> - Aaron.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 13 00:12:23 2005

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.