On Tue, Oct 27, 2009 at 2:27 PM, MB Software Solutions, LLC
<[email protected]> wrote:
> In our Best Practices document here at the day-job, we advise our
> customers to exclude our program and data folders from the A/V scans.
Me too. Speaking of which, has anyone come across the SMB2 issue with
delayed file creation?
It only affects Vista/Windows 7 & Windows Server 2008 (XP+2008 is OK,
Vista/7+2003 is OK).
There can be a 10 second delay after creating a file on a network
drive before it appears in the directory.
So if you do something like:
COPY "src.txt" TO "dst.txt"
IF File("dst.txt")
...
ENDIF
The File() call can fail. Actually I'm not sure if File() has a
problem but something like ADIR() certainly does. One solution is to
switch off SMB2, but I don't particularly like that.
See:
http://blogs.msdn.com/winsdk/archive/2009/07/10/file-exists-access-getfileattributes-findfirstfile-findnextfile-stat-behavior-over-smb-2-0.aspx
Problem Observed: When an application on client creates a file on a
shared directory on server or application on server creates a file on
shared directory on server, and file is created successfully but when
the application on client try to check the existence of the recently
created file by _access or other method, it reports that the file does
not exists. This behavior is observed when SMB 2.0 is used.
--
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
