Is your trace below only showing traffic from client to SVN server? If
so, try grabbing all traffic from the client to see what else may be
going on. There are a couple features of SSL which may explain this.
First, does your certificate signing chain include intermediary
signers? An exampl
--parent-dir Folder1 /path/to/svn/repo < folder1.dump
- svnadmin load --parent-dir Folder2 /path/to/svn/repo < folder2.dump
- svnadmin load --parent-dir Folder3 /path/to/svn/repo < folder3.dump
Victor Sudakov wrote:
Brian Brophy wrote:
I migrated a large CVS repository (25-50 GB) to SV
I migrated a large CVS repository (25-50 GB) to SVN years ago on SVN
1.3. Our repo had many sections (projects) within it. We had to
migrate each project independently so that it's team could coordinate
when they migrated to SVN. As such, I dumped each project when ready
and then svnadmin lo
I realize this is not directly related to SVN itself; however, I am
hoping this community may have some suggestions. If there is a more
appropriate forum I should be engaging, please let me know.
We have a repo with over 125 GB of data, containing everything from
source code to requirements d
We also use Veritas Clustering. Yes, it is overkill, but in a corporate
world this sometimes happens. SVN clients are purely on the HTTPS
interface so Apache is our service-facing client view. There are (2)
Red Hat Enterprise Linux servers using a SAN to persist the repository
data. Veritas
