hey freeRADIUS users, I'm trying to syslog the radius-messages with freeradius 1.1.2! Now I've added the line log_destination = files to the radiusd.conf, and I also tried to start the radius with the parameter -lsyslog but nothing goes to syslog! Any ideas?!? thanks mIke
Michael Messner <michael.messner_edv@inode.at> wrote:
to the radiusd.conf, and I also tried to start the radius with the parameter -lsyslog but nothing goes to syslog!
That doesn't really work in 1.1.x Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On Wednesday 04 October 2006 12:27, Michael Messner wrote:
hey alan,
Alan DeKok wrote:
Michael Messner <michael.messner_edv@inode.at> wrote:
to the radiusd.conf, and I also tried to start the radius with the parameter -lsyslog but nothing goes to syslog!
That doesn't really work in 1.1.x
any workarounds available?
Make the log file a named pipe (see mkfifo) and write a program that reads from the pipe and sends the messages to the local syslog daemon. Ugly hack.. but it should work as long as your reader program starts before freeradius. Other options would be to look at the cvs head changes that added the extra logging options and backport those to your local copy, or run a nightly snapshot. Kevin Bonner
try ... log_destination = syslog log { syslog_facility = daemon } Michael Messner wrote:
hey freeRADIUS users,
I'm trying to syslog the radius-messages with freeradius 1.1.2!
Now I've added the line
log_destination = files
to the radiusd.conf, and I also tried to start the radius with the parameter -lsyslog but nothing goes to syslog!
Any ideas?!?
thanks mIke - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Thursday 05 October 2006 08:07, Michael Messner wrote:
hey kenneth,
Kenneth Grady wrote:
try ...
log_destination = syslog log { syslog_facility = daemon }
not working :-(
mIke
I don't believe it was added to the 1.1.X branch, so the CVS head and nightly snapshots are the only way to use the syslog logging method. Wait for 2.0 or try one of the other suggestions in my previous email. Kevin Bonner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hey Kevin, Kevin Bonner wrote:
On Thursday 05 October 2006 08:07, Michael Messner wrote:
hey kenneth,
Kenneth Grady wrote:
try ...
log_destination = syslog log { syslog_facility = daemon } not working :-(
mIke
I don't believe it was added to the 1.1.X branch, so the CVS head and nightly snapshots are the only way to use the syslog logging method. Wait for 2.0 or try one of the other suggestions in my previous email.
If I find time I'll take a look! thanks mIke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFJSvkyUY4xkIcFVQRAsWUAKCgYyG1FEsJDqpxvuya4NPrNzi6nwCfTYZy 5OhySuMRE0ZLNGu3Dl7ub9Q= =dfCc -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hey, Michael Messner wrote:
Kevin Bonner wrote:
I don't believe it was added to the 1.1.X branch, so the CVS head and nightly snapshots are the only way to use the syslog logging method. Wait for 2.0 or try one of the other suggestions in my previous email.
If I find time I'll take a look!
with a pipe to "logger" it works good for me now! thanks mIke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFLQo6yUY4xkIcFVQRAu5VAKDZD6E/sFSfAYP1qzHSbZA/GQA6IQCgrPQr rSqv2cHeJOan8ouABKHBfl4= =f2Wv -----END PGP SIGNATURE-----
participants (4)
-
Alan DeKok -
Kenneth Grady -
Kevin Bonner -
Michael Messner