Correct, but you don't want to run it in a heavy production environment for very long. While I don't have proof, it would HAVE to be less efficient because it isn't using threads and its taking the time to print everything. A little trick I use when I need to test something in production is to kill the process, run it like this... radiusd -X &> log ... then I will do my dialup test and look at the contents of log. All stdout and stderr will be there. When you have the information you need you can just restart the process without -X. Its necessary for me to redirect the output because our radius server can get up to 10 requests per second, far too much to simply look at as it comes in. Chris Carver Network Engineer On Fri, 2006-05-19 at 16:37 -0400, Dennis Skinner wrote:
Just do:
radiusd -X
You should be doing this on a test machine anyway. Debugging on a production system is tough.
It does not use any more system resources than running it in normal mode. It just prints what it is doing to the screen. Try it and see. It won't crash you system (unless your system is *VERY* unstable to begin with).
Giuseppe Parlato wrote:
maybe I found the solution looking at the wiki guide: radiusd -sfxxyz -l stdout
does it use much system resource?
Giuseppe
----- Original Message ----- From: Giuseppe Parlato To: FreeRadius users mailing list Sent: Friday, May 19, 2006 11:51 AM Subject: debugging mode
Hi, I want to look at Radius managing clients-database queries, however I'm quite afraid to crash my linux enabling debugging with radiusd -X command (or maybe I should do that at night). There is no other way to see Radius "actions"..not log. I want to learn more.
Thanks
Giuseppe
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.6.1/343 - Release Date: 18/05/2006 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html