[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Brent Webster <brent.webster_at_liquidcomputing.com>
Date: 2005-09-12 23:46:25 CEST

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:

        # 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
Received on Mon Sep 12 23:48:15 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.