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

Re: Client-side hooks issue (SOLVED, questions)

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 18 Aug 2009 15:11:06 -0400

On Tue, Aug 18, 2009 at 14:59, Aaron D.
Marasco<Trac-Mail_at_revragnarok.com> wrote:
> I am having the same issue that is described back in January in the archives
> -
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1312354
> .
>
> I cannot get any script to run. The error I always get is "The hook script
> returned an error:" in red text, then in the way bottom of the dialog it
> says, "The operation failed."
>
> (As I am typing the email, I get it working...) I can get it to work if I
> turn off Symantec Antivirus's real-time scanner. But that's not really an
> option for everybody. I was wondering what is going on behind the scenes
> that would kick off antivirus software? There should be a clean way to spawn
> off the process...?

If you read the full thread you linked, you'll see that you reached
the exact same conclusion as was reached there.

Some AV products hold exclusive locks on files longer than they
should. The Subversion libraries do make some accommodations here and
attempt several times to access those files (in hopes that they'll be
unlocked), but there is a time or attempt limit to prevent it from
going on too long.

Real-time scanners inspect files every time they're updated. No
specific action "kicks it off", that's just how it's designed to work.
The solution is to either replace it with a better-behaved package, or
instruct it to ignore your .svn directories.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2384905

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-18 21:11:18 CEST

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

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