Simon Butler wrote:
>
> hi all,i sent this in yesterday but no one response.. i know i'm
> flogging a dead horse but from all my searching around i
> can't find what the solution is for this issue.. can anyone help a
> newbie out!! :)
Judging by previous responses on this list to problems like yours, I'd
say your best bet is to dump BDB and use FSFS as the backend.
HTH,
Daniel Serodio
> hi, sorry i know this issue has come up a few times on the list but i
> still can't figure it out :(
>
> i have umask 002 for all the users on the system and i have g+s
> permissions on the repos. all the users are in the same
> group as the repositary owner. the issue seems to be when my
> co-developer comes in with a commit using sv+ssh, the log
> file in the db dir ends up with the wrong permissions. i had him set
> umask 002 on his remote account but this doesn't have
> any effect either..
>
> any clues would be most appreciated!!
>
> a more complete summary of the issue below..
>
> -------------------
>
> i'm using svn 1.2.3 and am sharing a repos with one other developer and
> i keep getting problems with the permissions on the repos
>
> i get:
>
> svn co svn+ssh://st...@blah.com/repos/svn/nlm
> Enter passphrase for key '/users/steve/.ssh/id_rsa':
> svn: Berkeley DB error for filesystem /repos/svn/nlm/db while
> checkpointing after Berkeley DB transaction:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: /repos/svn/nlm/db/log.0000000003: log file open failed:
> Permission denied
> svn: bdb: PANIC: Permission denied
> svn: bdb: DB_ENV->log_put: 3: DB_RUNRECOVERY: Fatal error, run database
> recovery
> svn: bdb: txn_checkpoint: failed to flush the buffer cache
> DB_RUNRECOVERY: Fatal error, run database recovery
> '
>
> when i go to the server and try to recover the database i get
>
> svnuser@blah repos/svn 12> svnadmin recover nlm
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svnadmin: DB_RUNRECOVERY: Fatal error, run database recovery
> svnadmin: bdb: nlm/db/log.0000000003: log file open failed: Permission
> denied
> svnadmin: bdb: PANIC: Permission denied
> svnadmin: bdb: DB_ENV->log_put: 3: DB_RUNRECOVERY: Fatal error, run
> database recovery
> svnadmin: bdb: txn_checkpoint: log failed at LSN [3 3819]
> DB_RUNRECOVERY: Fatal error, run database recovery
> svnadmin: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database
> recovery
> svnadmin: bdb: nlm/db/log.0000000003: log file open failed: Permission
> denied
> svnadmin: bdb: PANIC: Permission denied
> svnadmin: bdb: DB_ENV->log_put: 3: DB_RUNRECOVERY: Fatal error, run
> database recovery
>
> and the problem seems to be that the nlm/db/log.0000000003 keeps
> getting read only access after my friend has made an update
>
> 8 -rw-r--r-- 1 friend users 3907 Mar 9 13:07
> log.0000000003
>
> my friend has umask 002 set and also the repos has g+s set on the dir
>
> anyone know what i'm doing wrong here? how can i stop these logfiles
> from getting the wrong permissions?
>
> thx!!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 15 19:14:52 2006