hot-backup.py and umask

I run hot-backup.py on my repositories as root. All of a sudden, a repository became inaccessible due to the db log file not having svn group write permissions. The solution is to (temporarily) change to umask 002 for the hot-backup.py command, or to use the setgid wrapper scripts often mentioned on this list for the command "svnadmin hotcopy --clean-logs". But the svnadmin command path is hard-coded (after building) in the script.

Have we currently nailed down the best way to implement the setgid wrappers on UNIX? Can it please be part of the build/install process? Just when I thought I had everything stable, the backup procedure suddenly throws things for a loop!

cheers,
        Simon

--------------------------
NOTE: This message and any included attachments are from HealthCom Partners, LLC and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 21 18:24:32 2004