Hi All,
In my last email, I wrote:
> I have a server has two separate repository simultaneously, using
Apache over HTTPS. OS is FreeBSD. Subversion is 1.0.6. I want to run
hot-backup.py everyday for each of the repositories. But only one repository
is successfully backup'ed. The other one got an exception:
Actually there is another serious problem. Some developers want to
control the access of a repository. They may add a new dir and set somebody
can read it and others cannot. Because the server is using authz_svn_module,
this means they must modify the ini file in server. But i don't want to add
their system accounts to login server directly, I use a simple method: put
the ini into the subversion, and use crontab to update the ini constantly.
In this way they can modify the ini in svn and commit changes, wait for the
ini take effect.
The command in crontab is:
cd /home/apache2/etc && /usr/local/subversion/bin/svn cat
file:///home/svn_repos/admin/svn_arkstudio.ini > svn_arkstudio.ini.tmp && mv
svn_arkstudio.ini.tmp svn_arkstudio.ini
Everything seemed well at the first several hours. And then I got
email from crontab and tell me:
svn: Unable to open an ra_local session to URL
svn: Unable to open repository
'file:///home/svn_repos/admin/svn_arkstudio.ini'
svn: Berkeley DB error while opening environment for filesystem
/home/svn_repos/db:
DB_RUNRECOVERY: Fatal error, run database recovery
And I login the server and run svnadmin recover, the repository
became fine again. But after some hours, the problem appeared again. The
repository had run well for a few months, so I think it must the command in
crontab trigger this issue.
Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 5 16:27:35 2004