Maybe it is something to enforce time integrity across clients? Or concurrent access of the same file?
I.e. make the Create/Open fail if the CreateTimestamp of
the existing file is in the future compared to the specified TWrp
timestamp?
On 2/6/06, ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote:
In one capture I have seen a new extrainfo tag for the Create call.
It is used in the Create Request (but is not returned in the Response)
It was used when some application opened the file '@'
with Disposition : 1 if file exists open it, else fail
The create flags contained the bit 0x00200000 which i dont know what it means.
The file was opened on a normal share.
The tag is
TWrp
and it is followed by 8 bytes of data, 8 bytes that are definitely a 64bit timestamp.
The weird thing is that this timestamp is slightly in the future.
It is about ~0x0000000020000000 larger than the "current" time of the server
The file was apparently already created (but i can not see when)
which might explain why this timestamp is slightly in the future
compared to the
Create/Write/Access timestamps of this file.
