
CHAPTER G
G - 18
Invalid socket path '<socket path>': <OS error>.
Explanation: The user has given invalid socket path from configuration file or from
command-line, either socket does not exist or is not accessible.
Resolution: fsav exits with fatal error status (exit code 1). The user has to correct the
command-line parameters or configuration file or remove the file from path and start
the fsav again.
Input file '<file path>' is invalid: <OS error>.
Explanation: The user has given invalid input file path, either file does not exist or is
not readable.
Resolution: fsav exits with fatal error status (exit code 1). The user has to correct the
command-line parameters and start the fsav again.
Unknown command line option '<option>'.
Explanation: The user has given unknown option from the command-line.
Resolution: fsav exits with error status. The user has to correct the command-line
parameters and start the fsav again.
Could not open configuration file <file path>: <OS error>
Explanation: The user has given a file path to the
--configfile
option which either
does not exist or is not accessible.
Resolution: The user has to correct command-line options and try again.
Scan engine directory '<directory path>' is not valid in configuration file at line
<line number>: <OS error message>
Explanation: The user has specified a scan engine directory path which either does
Summary of Contents for LINUX SECURITY
Page 1: ...F Secure Linux Security...
Page 2: ......
Page 14: ......
Page 28: ......
Page 32: ......
Page 84: ...Note Press ctrl C to cancel your changes 84 F Secure Linux Security Command Line Tools...
Page 150: ...CHAPTERG G 31 For more information see F Secure home page...
Page 166: ...CHAPTERG G 47 dbupdate 8 fsav 1 For more information see F Secure home page...
Page 170: ...CHAPTERG G 51 fsav 1 and fsavd 8 For more information see F Secure home page...
Page 188: ...H 69 H Config Files fsaua_config 70 fssp conf 75...