Re: post-commit update hook locking wc

"chris feldmann" <cfeldmann@gmail.com> writes:
> I have a variety of websites in repositories on a webserver where the
> webroot for each repo is checked out working copy on the same
> webserver. For some time now I've used post-commit hooks that call a
> small c binary i made that just execl's the subversion update command
> on the web root working copy from the repository that receives the
> commit. This way, of course, I can work locally on a wc, commit it,
> and reload the website to see the changes in the webroot wc.
>
> But recently (2 days ago), the hooks started leaving the webroot wc in
> a locked state. It appears that the hook is locking the wc itself
> immediately before updating (it writes an empty lock file to the top
> level .svn dir). The update then fails silently. Obviously something
> changed since this method had been working fine for almost a year, but
> I'm not even sure where to start looking. Or which of the other devs
> to start blaming :)

It fails silently? (It's 'svn' itself leaving the lock, by the way,
not your hook script per se.)

So there's no error output at all? Are you positive that when you
attempt to reproduce this by hand, your UID and environment are
exactly the same as that under which the hook executes? See

   http://subversion.tigris.org/faq.html#hook-debugging

-Karl

-- 
Subversion support & consulting  <>  http://producingoss.com/consulting.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org