On 07/18/2011 06:27 PM, Nico Kadel-Garcia wrote:
On Mon, Jul 18, 2011 at 7:10 AM, Erik Huelsmann<ehu...@gmail.com>  wrote:
I would think that it looks at SVNParentPath and tries to treat every

subdirectory of that as a repository.
Not quite. It's not "every subdirectory", it's "every child
directory". Â That means it will not descend into subdirectories of
subdirectories, fir example, so they all need to be right there in
/var/svn. Also, while symlinks to other locations may be acceptable to
the mod_dav_svn module, the repositories need to be accessible to the
"apache" user. This can get adventuresome if you're running svnserve
or svn+ssh access without a devault svn+ssh user, used in parallel to
Apache.
While links are acceptable to mod_dav_svn, they won't appear in the
repository listing. Note that you need the SVNListParent On statement in
your Apache config to get a listing of the repositories.
In 1.7 I've committed a small change to list symlinks to directories which
will be part of 1.7.

Bye,
Erik.
Cool, but be careful with those. If you have SELinux enabled and the
repositories are elsewhere, for example on a separate disk for bulky
repositories, you may need to review your SELinux settings to enable
httpd access to the separate location.

And oh, dear lord, if someone starts putting symlinks in the
reponame/conf/ or reponame/hooks/, can you have adventures. (See
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=767435,
which was only recently fixed and the fix isn't in most public
Subversion releases.)

SUNNY BEACH!

If it's a hard link, editing the file will break the replication. If it's a symbolic link, a hotcopy will drop it. If the symbolic link were copied as a symlink, I need to link it to "../../conf/*" instead of "/Subversion/conf/*" so that my copied symbolic links point into the backup, not into the original.

So I have changed my create.php to relative, not abosolute, symlinks, and edited my SVNBackup.sh script to 'cp -p -d' the symlinks from the master to the backup.

Thanks for the heads-up.

Reply via email to