I've cant seem to use any configuration file - hammerhead just writes into my configuration file all the time.
the results of this are written into the test.conf where my custom configuration is placed - however the configuration itself is ignored - he seems to always use his configuration in /etc/hammerhead/ which is 127.0.0.1 .. whats the error here ?
check out the cvs version and build it. You can view the man page there for support about the new and changed options. Alternatively you can get fast options help with hammerheade --help on commandline (also cvs version).
I have the actual version of hammerhead and the manual is last updated of 15 Feb 2000 !
And it simply says hammerhead configFile
but that does not work - something has been changed - undocumented tho.
Not the sourceforge documentation webpage. That corresponds to the released version.
If you check out the cvs version, build it and install it it will include a man page.
Just saw that the version I'm talking about is released. The html doc page is not updated though.
I will fix this in the near future.
My mistake - I updated the man page (hammerhead.1) and
hammerhead.txt and forgot about the HTML version. I should
put it in the build process! Will update and add to CVS after
this note. Thanks for checking in Niklas!
Actually I should clarify that Niklas actually updated the
manual page, I just did hammerhead.txt (and not that recently
now that I look anyway). Both depend versions are now
build as part of the build process and should be in CVS.
Guys, i dont know what you are doing but there is no visual change you made in the documentation.
Here is the newest hammerhead.html
First - it still says Updated: 17 Dec 2001
Now i exactly tryed the test scenario..
My conf and scn file are in the folder :
My conf file :
# example configuration file - scenario1.conf
# find all scenarios in this directory
# put all log messages in this file
# Load all embedded images in each page returned by the port
# Simulate 50 users
# Force all sequences to be completed
# Sleep 100ms between each request
# Print a summary report every 1000 requests
# Run the test for 10 minutes
# Hammer goanna, on port 8080
my scenario file
# Example Scenario file - scenario1.scn
# Get the main page, then think for one second, then go to
# the next scenario
NTest Scenario 1
RGET / HTTP/1.0
STest Scenario 2
E<title>Hammerhead - exploring Hammerland</title>
E<link rev=made href="mailto:email@example.com">
# Get some random page, don't think, and go nowhere else
# NOTE: . at end of scenario not required at end of file
NTest Scenario 2
RGET /coma HTTP/1.0
Now based on your documentation i've done
And what happends ? The conf file in /etc/hammerhead/ is taken with the example files post.scn and root.scn - the results of the test are written into *my* scenario1.conf - my configuration, my scenario is ignored...
I have the latest version and your docs do not reflect this behaviour...
17th Dec 2001 was the last time the options changed (from the 15th Feb 2000 HTML version). From the .html manual page:
hammerhead [ options ] [ resultsFile ]
There are various optional arguments (listed below), the final argument is an optional results file; if you're putting your config file here then that's why it's being overwritten (sorry!).
Try 'hammerhead --help' for a list of options. Here is the
relevant section from the HTML manual page:
The following options are supported:
-s or --seconds
Seconds to run tests
-o or --outfile
Output result file
-t or --test
Test the scenarios in the conf file.
-C or --checkconf
Check config file
-c or --conffile
Config file path
-h or --help
Display help information
-v or --version
I hope that's helpful,
So an example call would be :
hammerhead -c scenario1.cnf
Is that correct ? Under
there is still this written :
The following example:
example% hammerhead test.conf
hammers the machine/port specified in the test.conf configuration file. "
The example is wrong (seems we missed that!). It should be something like:
hammerhead -c test.conf results.log
I've updated the docs to reflect that, thanks for pointing it out.