|
|
LICENSES
VFind requires a LICENSE file to run.
This LICENSE file is host specific, therefore VFind
will only run on the licensed machine. Additional licenses
may be purchased by contacting:
CyberSoft, Inc.
1508 Butler Pike
Conshohocken, PA 19428.
Phone: +1.610.825.4748
Fax: +1.610.825.6785
At start-up, VFind searches for the
LICENSE file in these locations:
- /LICENSE
- /etc/LICENSE
- The current working directory.
- The VSTK library directory configured during
installation.
INPUT
VFind can be run in three ways.
- Interactive mode: Running VFind without any file
arguments (or other input such as SmartScan and stdin)
will result in a prompt asking what file to scan.
Example:
vfind
- Batch mode: VFind can be invoked with a list of
files (or other input such as SmartScan or stdin). In this
mode, VFind will scan all of the targets and write a
report to stdout. This mode is useful when scanning many
files or directories.
Example:
vfind *.doc *.exe
- Automated mode: VFind can be run from a script,
batch file, or other application and be scheduled using
UNIX cron or a similar program. To run in this mode simply
create your VFind command and place it in the
appropriate place in your script, batch file, or
application. When this mode is invoked, VFind will run unattended and generate a report to stdout. This report can be redirected to a file, E-mailed, or otherwise processed. This mode of operation is useful when scanning a large amount of data on a regular basis.
OUTPUT
VFind's output can be very verbose at times.
In order to cut down the output we recommend using the choke
method.
The choke method is as simple as piping the output from
VFind into grep, or a similar tool.
Each line of output from VFind starts with a chevron as
follows:
| Chevron |
Meaning |
|
| ##==> |
Informational Message |
| ##==>> |
VFind Warning |
| ##==>>> |
Serious VFind Condition |
| ##==>>>> |
Possible Virus Detection |
Example:
find / -type f | vfind | grep '##==>>>' > REPORT
The above example would only show errors and virus
detection messages.
SMARTSCAN
VFind is a SmartScan compliant tool. Specifying
the -ssr option to VFind will cause VFind to read a SmartScan stream from stdin. For example:
find /export/home -type f -print | uad -s -ssw | \
vfind -ssr > REPORT
SPEED
Why would you ever want to use less than the maximum
speed? Most users will never have to worry about this;
however, here are a couple of reasons someone might.
One reason is that there is a space/speed trade-off. With
--speed=2, VFind typically takes about 8
Megabytes of dynamic space to run. If this is prohibitive on
your machine (i.e., VFind can't run or there
is excessive paging),
try --speed=1.
Another reason involves the trade-off between start-up
time and marginal scan time. With --speed=2 there is a
substantial start-up time as VFind initializes
various
internal structures. This might be on the order of, e.g.,
a second. When scanning a single small file, this might be
a waste of time.
On the other hand, --speed=2 provides the fastest marginal
scan time, that is, the time needed to scan each extra
byte of data. Thus, when scanning large amounts of data
with a single invocation of VFind (such as when
handling SmartScan data from uad(1) or handling a large
number of file names piped in via standard input),
--speed=2" (if you have the space for it) is a good idea
despite the start-up time.
|
|