Hi,
we're running a SVN repo (~6GB) on 1.7.3.
Checking out the entire repo in one "svn co" (both 1.6 and 1.7) session is
almost impossible.
The httpd process starts consuming up to 4GB and then dies, killing the svn
client process with:
svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read
Hi,
answering my own post:
* Fridtjof Busse :
>
> The httpd process starts consuming up to 4GB and then dies, killing the
> svn client process with:
> svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read chunk size:
> connection was closed by server
Setting the configuration to
SVNAllowBu
Am 05.03.2012 09:30, schrieb Fridtjof Busse:
we're running a SVN repo (~6GB) on 1.7.3. Checking out the entire
repo in one "svn co" (both 1.6 and 1.7) session is almost
impossible. The httpd process starts consuming up to 4GB and then
dies...
Note: The repository size and the size of a checkout
Presumably, tcpdump/wireshark of the response headers will be useful.
Daniel
(no time to dive deeply into this right now, sorry)
Fridtjof Busse wrote on Tue, Mar 06, 2012 at 12:44:06 +0100:
> Hi,
>
> answering my own post:
>
> * Fridtjof Busse :
> >
> > The httpd process starts consuming up to
* Daniel Shahaf :
> Presumably, tcpdump/wireshark of the response headers will be useful.
The problem was very subtle:
Apache delivered a P3P header (our own configuration). This broke the checkout.
Why only a certain file was affected (it worked when the file was not in the
repo) or why it worke
