summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorvenaas <venaas>2007-05-07 13:03:35 +0000
committervenaas <venaas@e88ac4ed-0b26-0410-9574-a7f39faa03bf>2007-05-07 13:03:35 +0000
commitaad355533c7afbfde3b95653737e280f70a12bcb (patch)
treee5937e29d3883c069b2d8aa1be0b356703214571 /README
parentb3e8a445cc1e337ab924e37c6a3b5b0b48162a79 (diff)
Detach as default, options for foreground and debug level
git-svn-id: https://svn.testnett.uninett.no/radsecproxy/trunk@75 e88ac4ed-0b26-0410-9574-a7f39faa03bf
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 14 insertions, 8 deletions
diff --git a/README b/README
index ee65233..f541519 100644
--- a/README
+++ b/README
@@ -1,16 +1,22 @@
-This is the very first experimental version of a generic RADIUS proxy
-that can support various RADIUS clients over UDP or TLS (RadSec).
+This is a beta version of a generic RADIUS proxy that can support
+various RADIUS clients over UDP or TLS (RadSec).
-It should build on most Linux platforms by simply typing "make".
-To use it you need to create three config files. These are the
-main config file "radsecproxy.conf" and server and client files
-"servers.conf" and "clients.conf". See the enclosed example files
-for further instructions.
+It should build on most Linux and BSD platforms by simply typing
+"make". To use it you need to create three config files. These
+are the main config file "radsecproxy.conf" and server and client
+files "servers.conf" and "clients.conf". See the enclosed example
+files for further instructions.
The config files must be in either "/etc/radsecproxy" or the
proxy's current work directory. You may alter the path near
the top of radsecproxy.h if necessary.
+There are two options that may be specified on the command line.
+They are "-d loglevel" to set a loglevel of 1, 2 or 3 where 3
+is the most detailed logging. Also "-f" to run the proxy in
+the foreground with logging to stderr. Without "-f" the default
+is to detach as a daemon and log to syslog.
+
For more information, feedback etc. contact <venaas@uninett.no>.
-Stig Venaas, 2007.01.08
+Stig Venaas, 2007.05.07