README #1

p4gremlin - a Perforce server stress tester

===========================================
										
Usage:

 p4 set P4GREMLIN=c:\somedir
 p4gremlin [user]

If a username is specified, p4gremlin will run as that username - if not, it 
will generate one randomly.

If no client exists, p4gremlin will create a new one named USER-HOST.  The 
client root will be under $P4GREMLIN\USER.

The gremlin will automatically reject any server whose port is 1666, since 
this is the most commonly used port for production servers - the 1666 will be 
substituted with "XXXX" before any commands are attempted.

Once you have started the program, it will run until killed, executing a wide 
array of Perforce commands (and possibly taking up a bit of local disk with 
its client workspace, to say nothing of memory, CPU, and network IO, which 
it will max out if at all possible).

Fatal errors will be printed to stderr, as well resolve help information - 
the former is by design, the latter is not - I'm still trying to figure out 
what channel that text comes in on so I can suppress it.

=====

Building:

Put the P4 Client API header files in your include path, and link in the 
appropriate libs as described in p4api.txt:
 http://www.perforce.com/perforce/doc.021/user/p4api.txt



Feedback and flames go to samwise@perforce.com.