summaryrefslogtreecommitdiff
path: root/source4/torture/basic/delaywrite.c
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r3888: Just proving :-) to tridge that a Setfileinfo with a modifiedJeremy Allison1-2/+17
write time is sticky, and causes any subsequent writes not to update the last write time. Added write that extends the file followed by fnum specific smbflush. It stays the same time :-). Jeremy. (This used to be commit a2ea2166dcb7044d7b9e53417e53febea2f81e20)
2007-10-10r3887: Much better understanding of delayed write time, and the interactionJeremy Allison1-4/+80
with setfileinfo modifying the write time. I have some ideas on how to emulate this in the Samba server now but the commented case will be very hard... Jeremy. (This used to be commit c9211d084719a16f671b315a9c0bc6ed59fa8c8e)
2007-10-10r3886: Trying to understand delayed file write update times. Added anotherJeremy Allison1-0/+97
test that uses 2 connections and queries the time via pathinfo, not fileinfo. MSDN states : "When writing to a file, the last write time is not fully updated until all handles used for writing have been closed." - but this is obviously untrue. W2K3 seems to use a 2 second granularity for this. Next I'll try using SetFileTime equivalent to see if this takes the same time to take effect. Jeremy. (This used to be commit 2e47e241f98c3dba8be346cea726def38399eb97)
2007-10-10r3699: - split the delayed write testing out of RAW-WRITE, as it is not yetAndrew Tridgell1-0/+284
clear what the correct behaviour is for delayed stat info update. - use a common torture_setup_dir() function for setting up a test directory in torture tests. (This used to be commit f7fb34715b7d6ea3c35ddd684cfb27459a420339)