Subversion 1.2.3 write-lock remain even with umask set to 2

[Brent Webster <br...@liquidcomputing.com>]

Reinstalled the latest release of Subversion (1.2.3) after a disk crash
on my server.  I notice the "swrepos/db/write-lock" file remains after a
successful commit. A suggestion was made to ensure the "umask 002"
wrapper was setup.  I forgot that so I created the follow wrapper:

	#!/bin/bash
	#
	# Wrapper script to ensure svn and any other subversion
executables are run with umask set to 2
	#
	umask 002
	${0}.orig $@ <mailto:$@"#!/bin/bash> 

The svn, svnadmin and svnlook scripts were all renamed with a .orig
extension then symbolic links were setup. i.e.
    ln -s ./svn.orig svn
 
During testing I added extra echo text to ensure it was being invoked
properly.  In any case, the write-lock file is still be left around and
owned by the userid who invoked svn+ssh command.
 
Any ideas????
 
Thanks, Brent