Re: Polymon and udp2tcpd

From: Alex Rousskov (
Date: Mon Dec 27 1999 - 11:06:41 MST

On 27 Dec 1999, Alan Smithee wrote:

> Poly-2.2.8 comes with polymon and udp2tcpd. How can I use them?

Polymon tool was introduced in Poly 1.3.1:

1.3.0 -> 1.3.1
    - added the "--notify" option that enables notification messages to be
      sent to a monitoring program; messages (currently less than 100
      bytes) are sent via UDP every 20 seconds.
    - added "--label" option to specify a [short] run description; the
      label gets included into notification messages if any.
    - added udp2tcpd, a daemon that runs on port 18256 (default), listens
      to notification messages (UDP), and forwards them to polymon(s) via
      TCP; the intention is to support multiple monitoring programs for
      the same notification stream without using IP multicast or broadcast
    - added polymon; a ncurses-based program that monitors run-time status
      of Polygraph experiments using udp2tcpd daemon

The only noticeable change since the first release is 108-byte packets
that are sent every 5 seconds (or whatever you set --stat_cycle to).

Here is a brief usage summary, please let me know if something is unclear.

1. When you start polyclt and polysrv processes, use the --notify

        clt> polyclt ... --notify
        srv> polysrv ... --notify

Where is the address of the machine you use for monitoring
purposes. Client and server machines must be able to talk to your
monitoring machine via UDP, at least. 18256 is the default port for
udp2tcpd (see change.log above).

You probably want to use --label option if you run more than one test
at a time.

        clt1> polyclt ... --notify --label no-proxy
        clt2> polyclt ... --notify --label my-fill-36

0. Start udp2tcpd daemon on the monitoring machine:

        mon> udp2tcpd

2. Start polymon(s). If you start a polymon process on the monitoring
machine, no parameters are needed. Otherwise, specify the address
where udp2tcpd is running. You can start as many polymons as you want
(convenient for giving your boss access to current test status and
monitoring the tests yourself).

        mon> polymon
        somehost> polymon

3. Browse polymon "screens" with left and right arrows on your
   keyboard. Most screens are self explanatory. To see clients
   (servers) only, use 'i' (currently works only if your client
   (server) IPs are odd (even)). To see one experiment only, use up
   and down arrows (relies on --labels).

Disclaimer: polymon uses ncurses library, the only choice short to Java
which I find ugly and unportable (ncurses, not Java). It runs well on
our FreeBSD boxes and compiles on some other machines. Polymon has a few
bugs; if it dies, just restart it. Polymon performance or presence
cannot affect the results of the test.


This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:10 MDT