#/bin/csh 
# Copyright 14 April 1999 by CyberSoft, Inc.
#
#                    What is Special About This Script
# This script runs VFind from the VSTK/P tool kit faster than most other
# scripts.  That is because it ignores NSF mounted drives, files that are
# of special types (such as device type files) and ignores FIFO files.
#
#                              Values
# This script run over a telenet session to a heavily used Sun Sparc 20
# executing Solaris 2.6 with 171,731 files, 113,112 live virus samples,
# 6 active Samba connections, 6 active POP3 connections, 2 active NFS
# connections, sendmail, modem traffic and 4 active telnet sessions at 
# the rate of 32,402 files per hour.  That is 54 files per minute on
# an already overloaded system using VFind Version 9.3.2.
#
#                          What does it do
# This script is used to determine how fast VFind can run on your
# system.  It increases disk utilization by writting a very large 
# report at the same time it is reading the disk.  Finally, to 
# measure your system use the head command to read the start date
# and time (head vfresults) then use the tail command to read the
# number of files searched, the number of viruses found and the ending
# date and time.  Subtract the times to find the number of hours of
# operation then divide by the number of files scanned.  This number
# is the VFind Throughtput Number (VTN).  The VTN can be improved
# in many ways including making sure your system is correctly balanced
# and by upgrading to newer versions of VFind.
#
#                        What Else
#
# It is easy to modify this script to actually run vfind in 
# unattended mode.  The most important part of the script is the
# options for the "find" command.  Change the find command options in
# your current operational script for these and it should improve your
# VTN for operations.  Make sure that you fully test these options on
# your system since these were only tested on Sun Microsystems Solaris
# 2.6 Sparc.  Finally, we have noticed that some versions of "find" 
# will accept command line options and ignore them.  For example we
# have noticed that the "-type f" option will sometimes still allow
# fifo files to pass to output.  Since fifo files are never ending,
# VFind will never complete scanning them.
#

rm -f vfresults
date >> vfresults

find /  \( \( -type f -a -local -a ! \( -name core \) -a ! \( -fstype proc \) \) \
	\) -print |     \
     ./vfind9.3.2 |cat - >> vfresults

date >> vfresults
