CHAPTER F
129
Explanation: The database update process has successfully
updated databases, but failed to remove the update flag file.
Resolution: fsavd is halted. The user should remove the
update flag file manually.
SCAN ERRORS
fsav scan errors are written to the standard error stream
(stderr). In case of scan error file scanning is immediately
stopped and the scan continues with next file in input. If no
files is found infected or suspected, the scan error is indi-
cated with exit code 9.
Scan erros reported by fsav and the descriptions are listed
below:
<file path>
: ERROR:
<OS error message>
Explanation: The file could not be scanned, reason is given in
OS error message.
Resolution: Common reason is the file does not exist or is not
readable. Check the file path and access rights.
<file path>
: ERROR: path too long - NOT
SCANNED
Explanation: The file path is too long ( > PATH_MAX). The file
cannot be scanned.
Resolution: The user has to move the file to a shorter path
and try to scan the file again.
<file path>
: ERROR: Could not open the file
Summary of Contents for ANTI-VIRUS LINUX CLIENT SECURITY -
Page 1: ...F Secure Anti Virus Linux Server Security Administrator s Guide...
Page 36: ...34 5 USER INTERFACE BASIC MODE Summary 35 Common Tasks 36...
Page 88: ...86 C Riskware Types Riskware Categories and Platforms 87...
Page 91: ...CHAPTERC 89 Riskware Types...
Page 104: ...102 F Man Pages fsav 103 fsavd 137 dbupdate 155 fsfwc 159 fsic 162...
Page 160: ...158 SEE ALSO fsav 1 and fsavd 8 For more information see F Secure home page...
Page 173: ...171 G APPENDIX Config Files fsaua_config 172 fssp conf 177...
Page 206: ...204...
Page 207: ......
Page 208: ...www f secure com...