fixed a bug with possible segfault in tcpconnect code, updated radsecproxy.1

git-svn-id: https://svn.testnett.uninett.no/radsecproxy/trunk@476 e88ac4ed-0b26-0410-9574-a7f39faa03bf

1 files changed, 30 insertions, 2 deletions

diff --git a/radsecproxy.1 b/radsecproxy.1
index f4d7760..8fc21af 100644
--- a/radsecproxy.1
+++ b/radsecproxy.1
@@ -1,10 +1,11 @@
-.TH radsecproxy 1 "2 October 2008"
+.TH radsecproxy 1 "17 February 2009"
 
 .SH "NAME"
 radsecproxy - a generic RADIUS proxy that provides both RADIUS UDP and TCP/TLS (RadSec) transport.
 
 .SH "SYNOPSIS"
-radsecproxy [ -c configfile ] [ -d debuglevel ] [ -f ] [ -p ] [ -v ]
+.HP 12
+radsecproxy [-c configfile] [-d debuglevel] [-f] [-i pidfile] [-p] [-v]
 .sp
 
 .SH "DESCRIPTION"
@@ -31,6 +32,7 @@ a proxy on a site boundary. Since the proxy \fBsupports both IPv4
 and IPv6\fR, it could also be used to allow communication in cases
 where some RADIUS nodes use only IPv4 and some only IPv6.
 
+.SH "OPTIONS"
 .TP
 .B -f
 .sp
@@ -75,6 +77,32 @@ information and exit.
 This option allows you to specify which config file to use. This is useful
 if you want to use a config file that is not in any of the default locations.
 
+.TP
+.B -i <pid file path>
+.sp
+\fIPID file path\fR
+.sp
+This option tells the proxy to create a PID file with the specified path.
+
+.SH "SIGNALS"
+The proxy generally exits on all signals. The exceptions are listed below.
+
+.TP
+.B SIGHUP
+.sp
+When logging to a file, this signal forces a reopen of the log file.
+
+.TP
+.B SIGPIPE
+.sp
+This signal is ignored.
+
+.SH "FILES"
+.TP
+.B /etc/radsecproxy.conf
+.sp
+The default configuration file.
+
 .SH "SEE ALSO"
 radsecproxy.conf(5), RadSec internet draft
 http://tools.ietf.org/html/draft-ietf-radext-radsec