Hello Jake!
> Thanks for your quick response. I think from the fsvs side, it might be good
> to improve
> the error message, but any fix would probably have to be made upstream (svn
> or openssh).
> Let me know if there's anything else I can do to help.
Well, I just committed ~80M without any problem:
$ fsvs ci -m1
Committing to svn+ssh://localhost/tmp/A/r
N... 79437009 large_file
committed revision 1 on 2009-05-28T06:43:48.832022Z as flip
And looking at your logfiles only shows me that the SSH process quit with an
error:
17135 19:05:23.768334 exit_group(-1) = ?
The SIGPIPE is only because FSVS tries to abort the commit, because it gets an
error -
but as the connection is dead, this doesn't work either ;-/
Which version of the subversion libraries are you using? 32bit, 64bit?
Please try something like
top -b0.1 | grep svnserve
while trying that commit; maybe there's some ulimit or memory leak, and the
server
process gets killed.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2356090
To unsubscribe from this discussion, e-mail:
[[email protected]].
