1. 4NHCT_Update.exe Driver
2. readme.txt File Contents

readme.txt Driver File Contents (4NHCT_Update.exe)

DOCMENT HOW TO RUN GQSTRESS
---------------------------

Server side setup (Cluster)
--------------------------

On the shared drive create a directory to store the html files for gqstress. (Typically InetPub\wwwroot\gqstress).

copy kinglet\rats\testsrc\kernel\cluster\clntsrv\ftp\*.html to the about created ftp directory on the shared drive.

create a IIS virual www root resource to point to gqstress directory (The directory that is created above). Give the virutal root name as /gqstress (This is hard coded)


Client side setup.
------------------


copy the following files to the client m/c.
kinglet\rats\testsrc\kernel\gibralter\gqstress\$(O)\gqstress.exe 
kinglet\rats\testsrc\kernel\cluster\clntsrv\ftp\*.cmd

The program to run gqcont.cmd <cluster name>

e.g. gqcont.cmd wolfcluster1

LOG
---
This program will spit "Failed"  to a text file (gqcont.log)

USAGE OF GQSTRESS.EXE: (Not required for client server testing)
---------------------

The usage of the gqstress.exe is described below.

gqstress usage:
gqstress [-v] [-h<htm file>] [-w<alias>] [-l#] [-t#] [-d] [-b#]

where:
  -v  verbose, displays all the pages read from server.
  -s<server name> server name or ip address to test.
      default servers are listed in gqstress.ini file.
  -w<virtual path> virtual path on the web server to find gqstress.htm.
      default is /gqstress.
      server name is in the gqstress.ini file.
  -h<htm file> specifies a html file to use for testing.
      must be full alias e.g. /gqstress/gqstress.htm
  -l# - where # is number of times to loop, 0 is indefinite.
  -t# - where # is number of threads to launch queries.
  -d - dump additional debug information.
  -b# - where # is seconds to wait for server response. 0 to block
  -c - randomly close socket after issueing query.
  -f - filter status, 0 - not finished, 1 - finished filtering
  -n - enable logging mechanism, logs to gqstress.log
  -u name password - run impersonating the give user
  -r# where # is number of times to retry in case of socket failure in clusterin g


e.g.
gqstress -ssivapad_cluster -l0 -b3 -r5 -h/gqstress/gqstress.htm


RESULTS:

It prints the query number and status of the query, whether it is passed or failed.