Even though rpld is small, it yet has a number of options to individually change its behavior. Most configuration file variables also have a command-line option counterpart. See the rpld.conf file for details. `rpld -?` will give you a brief overview of CL options available.

Logging is straightforward; as rpld is a non-interactive daemon, it runs in the background. Any output after initialization will go to syslog. Logfiles are put into the directory you specified 1. at the command line using -L, 2. rpld.conf or 3. /var/log/rpl, in that order.

Basically, every tty is monitored, but certain kinds are excluded, like the master side of BSD PTYs (major number 2) and Unix98 PTYs (major number 128 to 135), because they are just a mirror of their slave sides with things turned around.

Each packet recorded is also added a timestamp, but ttyreplay is not yet that advanced to display it.

ttyreplay is the tool to see -- to replay -- what has been captured by (the Kernel module and) rpld. Give it any number of files you want to see again.

Because some users and/or applications produce output in granulations finer than 1/HZ seconds, replaying these logs will make it look time is lagging. This is because the minimum delay a user-space application can do in non-priority scheduling mode for Kernels with HZ=100 (such as Linux 2.4) is 1/100 second. To circumvent this, use the -A option which turns on a special algorithm. More details about this can be found in the Tech section.