Norbert Unterberg wrote:
> Lübbe Onken schrieb:
>
>> The Subversion CL client is normally not affected,
>> because the virus scanners don't notice if something is happening
>> inside a
>> dos box.
>
>
> If that was true, I would throw my virus scanner away, since it would nt
> find virusses in command line programs. The svn command line tools are
> native 32 bit windows NT applications that are compiled for the console
> mode. All file i/o goes through the windows file system calls and are
> therefore checked by the on-access virus scanners.
>
> I am also very sure that the compatibility layer for old 16 bit DOS
> applications uses the windows file system calls and therefore are under
> control of virus scanners.
>
> So if the GUI is affected but command line tools are not, then there
> must be other differences.
It's not quite that easy:
- virus scanners really scan all files, even those from CL clients
- Subversion had (and probably still has) some issues with pool cleanup,
that means that sometimes file handles (if the first try fails because
of a virus scanner locking the file) aren't released after the function
finishes
- open file handles are closed automatically by the OS when the
application closes
- the CL client closes after every command, TSVN (the shell extension
part which does the 'svn st -v') is only closed when you logoff/reboot
- so when virus scanners interfere with Subversion and a file handle
doesn't get closed properly, then TSVN will stay in a 'locked' state,
but the CL client will work again on the next try.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Mar 21 17:08:13 2005