default linelog Accounting-Request handling broken?

Josip Rodin joy at entuzijast.net
Tue Dec 8 21:53:12 CET 2009


On Tue, Dec 08, 2009 at 11:32:36AM +0000, Alan Buxey wrote:
> Hi,
> 
> > Again, my point was that people who are prepared to immediately intervene in
> > a dead radiusd are most commonly are prepared to immediately intervene in a
> > faulty configuration file.
> 
> revisiting the early messages in this thread clearly indicate a
> desire for much more verbose logging of proxy issues....almost, if
> not exactly, a per-packer log when errors arise.  that is a 'bad thing'
> IMHO. much better to have the current situation.  you could
> argue - and I'll agree with it - that a tool like raddebug could be used
> to attach to the process and view the debug of proxy issues live
> and inline - just as it can be used for verbose client logging on
> a chosen station when not running the daemon in full debug.

But the proxy state logging is not a priori per-packet, it's based on status
check events. Only if each packet changes the proxy status (?!), then you'll
get as many status check logs as there are packets.

(This discussion is getting annoyingly circular.)

-- 
     2. That which causes joy or happiness.



More information about the Freeradius-Users mailing list