+.PP
+using sympathy to mimmick screen(1):
+.IP
+[foo@barhost ~]$ sympathy
+.IP
+.I Sympathy
+forks. The child becomes a daemon server and launches a new shell in a
+pseudo-tty, the original process becomes a client and connects to the server
+and shows the output. The user then uses the new shell and after some time
+either hangs up on the client or issues CTRL\-B quit, and the client detaches from
+the server.
+.IP
+Later the user wishes to retreive her session and to determine which sympathy
+sessions are active issues:
+.IP
+[foo@barhost ~]$ sympathy \-ls
+.br
+ barhost.2456 (Active)
+.br
+[root@square ~]$
+.IP
+The user then issues:
+.IP
+[foo@barhost ~]$ sympathy \-r 2456
+.IP
+and is reconnected to her session.
+.PP
+using sympathy to mimick minicom(1):
+.IP
+.IP
+[foo@barhost ~]$ sympathy -t -d /dev/modem -b 9600 -K
+.IP
+.I Sympathy
+opens the device /dev/modem and locks it, sets the baud rate to 9600 baud and disables
+flow control. A VT102 terminal emulator then displays the data from the modem. The user
+quits the emulator by issuing CTRL\-B quit, which unlocks the modem and exits sympathy.
+.PP
+using sympathy to mimick consolidate(1):
+.IP
+.IP
+[foo@barhost ~]$ sympathy -s -d /dev/ttyS13 -b 19200 -K -k /root/sympathy/13 -L /root/sympathy/13.log
+.IP
+.I Sympathy
+becomes a daemon and detaches from the current tty. It then opens the device
+/dev/ttyS13 and locks it, sets the baud rate to 19200 baud and disables flow
+control.
+.I Sympathy
+then listens for clients connecting on the socket -fI/root/sympathy/13-fP, whilst logging
+completed lines and changes in status to the file /root/sympathy/13.log.
+.IP
+A user wishing to see the current status of the /dev/ttyS13 issues:
+.IP
+[foo@barhost ~]$ sympathy -c -k /root/sympathy/13
+.IP
+and the last 200 lines of history are injected into the history of her outer
+terminal emulator and she is connected to /dev/ttyS13.