Adam wrote:
> Hi guys,
>
> I've also been seeing this a lot recently and had already assumed it
> was a virus scanner issue before finding this thread. I'm currently
> trying to get my IT to stop the McAfee on-access scanner from
> interfering with any TSVN processes.
>
> In the meantime I thought I would give the command line svn ago to see
> if they showed anything different in it's behaviour. The result was it
> did, it successfully committed the files. Unfortunately I realised to
> late that my command line installation was really out of date and was
> actually 1.5.0rc4 (doh!), so it might not be of much use if the
> problem is in one of the more recent svn builds.
>
> However it's definitely interesting that the process was still
> possible from another client. Maybe its worth others who use other
> clients, command line, subversive, subclipse could maybe try commits
> with these when they find TSVN stops working.
>
> While I agree that McAfee is at least partly to blame (I hate the damn
> thing!) if the effect is specific to TSVN rather than all SVN clients
> would this not be something that could be worked around?
>
> If I get another commit that fails I'll try what I've suggested above
> with a the v1.5.5 of the command line client.
The command line client is a console application. Virus scanners treat
console applications differently than windowed applications. That's why
the svn command line client is not as often affected by virus scanners
than TSVN is.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1187149
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-18 18:27:08 CET