-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey,
we start the radiusd in debugging mode and with the following line in
rc.local we now just get the loggin attempts into the radius.log:
tail -f /var/log/radius/radius_complete.log | grep --line-buffered \:\
Login /var/log/radius/radius.log
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt=logger -p local6.info -t radiusd -s
ARGS=-Afxyz
Michael Messner [EMAIL PROTECTED] wrote:
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
Because it's in debugging mode. Output goes to STDOUT, and not to
radius.log.
any
tail -F radius.log | logger
- Original Message -
From: Michael Messner [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, November 16, 2006 3:10 PM
Subject: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan DeKok schrieb:
Michael Messner [EMAIL PROTECTED] wrote:
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
Because it's in
: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt
Michael Messner [EMAIL PROTECTED] wrote:
Because it's in debugging mode. Output goes to STDOUT, and not to
radius.log.
sure, we need the possibility to analyze the files
Then why are you running the server in debugging mode, with output
goind to STDOUT?
I think this would be very
7 matches
Mail list logo
