The C-based command-line scanner of Symantec Protection Engine uses the following general syntax:
ssecls [-options] <path> [<path>...]
The <path> parameter lets you specify one or more files or directories to scan. Each file or directory must be separated by spaces. You can use the absolute or relative path. If the specified path is to a file, the file is scanned. If the path is to a directory, all of the files in the directory are scanned.
Do not use a path with a symbolic link. Symantec Protection Engine does not follow a symbolic link to a file.
You can specify any combination of files and directories. You must separate multiple entries with a space. For example:
You can specify any mounted file system, mount point, or mapped drive. For example:
Follow the standard formats for your operating system for handling path names (for example, special characters, quotation marks, or wildcard characters).
If you have specified a directory for scanning and want Symantec Protection Engine to descend into subdirectories to scan additional files, you must also use the -recurse option.
You can only specify files or directories for which you have appropriate permissions. To send files, you must have read access to the files. To repair (replace) or delete files, you must have permission to modify or delete the files. You must also have access to the directory where the files are located.
If you do not specify a path, input data is read from standard input (STDIN) and sent to Symantec Protection Engine for scanning. After the scan, the data (either the original file, if it was clean, or the repaired file) is written to standard output (STDOUT). If a file is infected and cannot be repaired, no data is written to STDOUT.
DBCS path names in scan requests should not be converted to Unicode (UTF-8) encoding before the path is passed to Symantec Protection Engine.