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):
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):
Access: Read Data/List Directory, Synchronize
Disposition: Open
Options: Synchronous IO Non-Alert, Non-Directory File, Complete If Oplocked
Attributes: n/a
ShareMode: Read
AllocationSize: n/a
and closes it.
ToirtoiseBlame then creates it twice (both succeed):
Access: Generic Read
Disposition: Open
Options: Synchronous IO Non-Alert, Non-Directory File
Attributes: N
ShareMode: Read, Write
AllocationSize: n/a
and:
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 one of the handles, then reads and closes the other one.
Does this help at all?
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1946023
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-27 16:06:51 CEST