Yes, I know that this executes locally under my credentials. I am also
aware that it executes in an empty environment.
I can execute the .bat file with correct results from the hooks
directory regardless of whether or not it is mapped to drive. The hook
does execute when the repository is mapped, but the exact same
repository connected to a UNC name doesn't execute the hooks.
I was not aware of the vulnerability under FILE://, but now that you
mention it, I'm guessing the problem arises when two (or more) people
try to commit (or otherwise modify) the repository at the same time.
Since FILE:// provides no directory level locking, you can get seriously
hosed. Is that the issue?
> -----Original Message-----
> From: Andy Levy [mailto:email@example.com]
> Sent: Friday, August 31, 2007 1:13 PM
> To: firstname.lastname@example.org; Strip, David R
> Subject: Re: Bug Report: Hooks not executed on repository
> connected via File to UNC path
> On 8/31/07, Strip, David R <email@example.com> wrote:
> > I have a repository on repository_host/svn If I connect to this
> > repository via FILE://repository_host/svn, TortoiseSVN
> doesn't execute
> > the hook scripts.
> > If, on the other hand, I first map repository_host to some
> drive, say
> > Z:, then if I connect to FILE://Z:/svn, the hook scripts
> are executed.
> > There are various bits and pieces of Windows that don't behave well
> > with UNC paths, perhaps this is related?
> Are you aware that when hooks execute when using file:///
> that the hooks execute on your local computer, under your
> credentials? This could present some issues with your scripts.
> If you're in a shared environment (multiple people using the
> repository), you should be aware that using file:/// is
> strongly discouraged and can lead to repository corruption or
> File:/// is meant for single-user, non-networked usage &
> testing. If you need to share a repository on a network, run
> a real (svnserve or
> Apache) server.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Aug 31 21:37:37 2007