-.P\r
-If the configuration file is not specified on the command line,\r
-\fBJunkbuster\fP will look for a file named \fIconfig\fP in the \r
-current directory (except on Amiga where it will look for \r
-\fIAmiTCP:db/junkbuster/config\fP and Win32 where it will try \r
-\fIconfig.txt\fP).\r
+\r
+.SH OPTIONS\r
+\fBJunkbuster\fP may be invoked with the following command-line options:\r
+.TP\r
+.BR --version " (unix only)"\r
+Print version info and exit.\r
+.TP\r
+.BR --help " (unix only)"\r
+Print a short usage info and exit.\r
+.TP\r
+.BR --no-daemon " (unix only)"\r
+Don't become a daemon, i.e. don't fork and become process group\r
+leader, don't detach from controlling tty, and do all logging\r
+there.\r
+.TP\r
+\fB --pidfile\fP \fIPID_FILE\fP (unix only)\r
+On startup, write the process ID to \fIpidfile\fP. Delete the\r
+\fIpidfile\fP on exit. Failiure to create or delete the\r
+\fIpidfile\fP is non-fatal. If no \fB--pidfile\fP option\r
+is given, no PID file will be used.\r
+.TP\r
+\fB --user\fP \fIUSER\fP (unix only)\r
+After (optionally) writing the PID file, assume the user ID\r
+of \fIuser\fP. Exit if the privileges are not sufficient to\r
+do so.\r
+\r
+.PP\r
+If the \fIconfig file\fP is not specified on the command line,\r
+\fBJunkbuster\fP will look for a file named \fBconfig\fP in the \r
+current directory (except on Win32 where it will try \fBconfig.txt\fP).\r