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.
Adam
On Feb 16, 11:21 am, Simon Large <simon.tortoise..._at_googlemail.com>
wrote:
> 2009/2/2 Divis, Jason <jason.di..._at_se2.com>:
>
>
>
> > I found the following discussion on svn.haxx.se and have a follow-up:
>
> > On Wed, 21 Jan 2009 07:31:15 -0800 (PST) TafT wrote:
> >> From within McAfee I created an exception so that the On-Access scanner
> >> does not scan any files within
> >> the root working directories .svn\ folder when they are either written or
> >> read. Before this change I could
> >> commit a handful of files successfully but not any complex directory
> >> structures. After this change I have
> >> managed to commit over 5000 files in a directory structure with at least 5
> >> levels to it.
>
> > I am seeing a similar situation, but with imports, instead of commits. I too
> > cannot disable the McAfee virus scanner in total. We've created the .svn\
> > exception, but since there are no .svn\ directories created on the local
> > machine, until a checkout is performed, I don't think that is my solution.
> > Is the work-around to add my working directory that I am importing from, to
> > the McAfee exception list?
>
> Tell you what. Since you have the PC which exhibits the problem and we
> don't, why don't you try it and see if it works, then report back :-)
>
> > I realize this is not just an TSVN issue, and that McAfee has its fair share
> > of blame, but it seems that this sort of question might help the TSVN
> > community as a whole, as the McAfee support isn't as accessible as the TSVN
> > support.
>
> Your input will be a valuable part of that community resource.
>
> Simon
>
> --
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> To unsubscribe from this discussion, e-mail: [users-unsubscr..._at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1184664
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-18 10:28:25 CET