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. alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
