If the file is being scanned on open, the open will return EACCES. Exactly what the user will see depends on the application / protocol etc being used to open the file.
If the file is being scanned on close, the scan is asynchronous and the user will not see any error. The file will simply remain marked as needing scanned and a scan will be attempted again the next time the file is accessed. Joyce Jason J. W. Williams wrote: > Hi Joyce, > > Thank you for the clarification. So users will receive an active error > message that they cannot access the file when this occurs? Rather than > a passive timeout? > > Thank you again! > > Best Regards, > Jason > > On Jan 7, 2008 11:01 AM, Joyce McIntosh <[EMAIL PROTECTED]> wrote: > >> By design, if a file that REQUIRES SCANNING** cannot be scanned >> (eg because the scan engine fails and there's no alternate scan engine, >> or the alternate fails too) access to the file MAY be denied, depending >> upon what criteria deemed the file as requires-scanning. >> If the file has been scanned before and has not been modified since >> then, access to it will be allowed. >> >> Joyce >> >> >> Jason J. W. Williams wrote: >> >>> Hi Guys, >>> >>> >>> >>>> Note: If any component such as the ICAP server, or ClamAV fails, all >>>> files in the protected filesystems are unusable until the condition >>>> causing the failure is fixed or virus scanning is disabled for protected >>>> filesystems. >>>> >>>> >>> Is this behavior by design? >>> >>> -J >>> >>> _______________________________________________ >>> storage-discuss mailing list >>> [email protected] >>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss >>> >>> >> _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
