Re: TortoiseBlame error

Nikki Locke wrote:
> Have just done so. Filtering access to just the relevant file reveals...
> TortoiseProc creates it (succeeds):
> Access: Generic Read/Write
> Disposition: OverwriteIf
> Options: Synchronous IO Non-Alert, Non-Directory File
> Attributes: N
> ShareMode:
> AllocationSize: 5,036,009,631,718,047,744
>
> TortoiseProc then tries to create it twice more (both fail):

This is misleading: Procmon shows "CreateFile", but that API is also
used to simply open a file. It doesn't really "create" the file again.
Also, the 'fails' are usually expected - the API tries to set
permissions and/or simply read them and get's a 'failed' if it doesn't
have full access to the file (which isn't required here).

> Access: Read Attributes, Synchronize
> Disposition: Open
> Options: Synchronous IO Non-Alert, Non-Directory File, Complete If Oplocked
> Attributes: n/a
> ShareMode: Read, Write, Delete
> AllocationSize: n/a
>
> It then writes data to it, tries to create it again (fails):
> Access: Generic Read
> Disposition: Open
> Options: Synchronous IO Non-Alert, Non-Directory File
> Attributes: n/a
> ShareMode: Read
> AllocationSize: n/a
>
> Creates it again (succeeds):
> Access: Read Attributes, Synchronize
> Disposition: Open
> Options: Synchronous IO Non-Alert, Non-Directory File, Complete If Oplocked
> Attributes: n/a
> ShareMode: Read, Write, Delete
> AllocationSize: n/a
>
> Closes it.
>
> The virus checker jumps in, tries to create it twice (fails):
> Access: Generic Read
> Disposition: Open
> Options: Synchronous IO Non-Alert
> Attributes: N
> ShareMode: Read, Write, Delete
> AllocationSize: n/a
> Impersonating: XENXP\nikki
>
> Then creates it agin (succeeds):
> Access: Generic Read
> Disposition: Open
> Options: Synchronous IO Non-Alert, Open For Backup
> Attributes: N
> ShareMode: Read, Write, Delete
> AllocationSize: n/a
> Impersonating: XENXP\nikki
>
> Reads it and closes it.
>
> TortoisePlink closes it (did it inherit the other file handle from TortoiseProc?), Creates it (success):

I think this seems like the problem: I guess you're using svn+ssh:// to
access your repository?
Even though I don't see why TortoisePlink should even touch that file -
it's only responsible for encrypting the network transfer...
Or did you mean TortoiseBlame here? If TortoiseBlame, then I suspect the
virus scanner hooking into the newly created TBlame process.

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=1948090
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].