.SH "SYNOPSIS"
.
.B tripe-uslip
-.RB [ \-gp ]
+.RB [ \-fgps ]
.I socket
.
.\"--------------------------------------------------------------------------
Connect to
.IR socket ,
read a packet from standard input and write it to the socket.
+.TP
+.B \-f, \-\-flood
+Connect to
+.IR socket ,
+and send packets as fast as possible. The packets sent aren't very
+interesting, and there's no way to configure their contents.
+.TP
+.B \-s, \-\-sink
+Connect to
+.IR socket
+and read packets as the become available. The packets are discarded,
+though if stdout is a terminal, a simple spinning-baton animation is
+updated once for each group of packets. If you are flooding one end of
+a TrIPE connection, it's advisable to attach a sink to the other:
+otherwise the destination
+.B tripe-uslip
+will attempt to consume all available memory, storing incoming packets
+until someone retrieves them.
.
.\"--------------------------------------------------------------------------
.SH "BUGS"
server. It is not expected to be useful in production environments. In
particular, it intentionally imposes no limits on queue lengths or
packet sizes, and its internals and interface (one packet per client
-connection) are not well-suited for high performance.
+connection) are not well-suited for high performance. That said, the
+flood option has worked well enough to expose bugs in
+.BR tripe 's
+behaviour under heavy loads.
.PP
If
.B tripe-uslip