POLYGRAPH-SERVER(1) User Commands POLYGRAPH-SERVER(1)NAME
polygraph-server - Web Polygraph server simulator
server [--option ...]
OPTIONS --help list of options
package version info
package build environment info
console verbosity level
dump request/replies/errors headers/bodies to console
limit size of individual msg dump
send notifications to a [remote] monitoring program
where to listen for (and respond to) meta-information requests
where to forward meta-information
decrease default fd limit
configuration file name
directories to search for cfg files
redirect console output
detailed binary log file
buffer size for binary log
store working set
load working set
log file for samples
buffer size for sample log
accept foreign requests or responses
statistics cycle length
system call to use for scanning ready files
priority level for urgent socket operations
use given addresses, do not lookup real interfaces
delete old IP aliases before adding new ones
exit after inactivity timeout
per-process r.n.g. seed
per-test r.n.g. seed
use URL set that is unique across runs
hush frequent error reporting for that long
generate content regardless of the URLs
Copyright (C) 2003-2006 The Measurement Factory, Inc.
SEE ALSO polygraph(7) - general information and a list of programs
http://www.web-polygraph.org/ - project web site
polygraph-server - Web Polygraph February 2010 POLYGRAPH-SERVER(1)
Check Out this Related Man Page
MERGELOGS(1) General Commands Manual MERGELOGS(1)NAME
mergelogs - merge and consolidate web server logs
mergelogs -p penlog [-c] [-d] [-j jitter] [-t seconds] server1:logfile1 [server2:logfile2 ...]
mergelogs -p pen.log 10.0.0.1:access_log.1 10.0.0.2:access_log.2
mergelogs -p pen.log 10.0.18.6:access_log-10.0.18.6 10.0.18.8:access_log-10.0.18.8
When pen is used to load balance web servers, the web server log file lists all accesses as coming from the host running pen. This makes it
more difficult to analyze the log file.
To solve this, pen creates its own log file, which contains the real client address, the time of the access, the target server address and
the first few bytes of the requests.
Mergelogs reads pen's log file and the log files of all load balanced web servers, compares each entry and creates a combined log file that
looks as if the web server cluster were a single physical server. Client addresses are replaced with the real client addresses.
In the event that no matching client address can be found in the pen log, the server address is used instead. This should never happen, and
is meant as a debugging tool. A large number of these indicates that the server system date needs to be set, or that the jitter value is
You probably don't want to use this program. Penlog is a much more elegant and functional solution.
OPTIONS -c Do not cache pen log entries. The use of this option is not recommended, as it will make mergelogs search the entire pen log for
every line in the web server logs.
-d Debugging (repeat for more).
Log file from pen.
Jitter in seconds (default 600). This is the maximum variation in time stamps in the pen and web server log files. A smaller value
will result in a smaller pen log cache and faster processing, at the risk of missed entries.
The difference in seconds between the time on the pen server and UTC. For example, this is 7200 (two hours) in Finland.
Web server address and name of log file.
Copyright (C) 2001-2003 Ulric Eriksson, <email@example.com>.
SEE ALSO pen(1), webresolve(1), penlog(1), penlogd(1)