Re: latest CVS 2.0 beta hang problem

[Alan DeKok <aland@deployingradius.com>]

A.L.M.Buxey@lboro.ac.uk wrote:
> *correction* thats the last 2 output lines from radiusd.log
> i dont have a radiusd -X output - i will see if i can trigger
> this behaviour with eg radtest or an EAP session on another
> test server.  the issue doesnt occur with 2.0.0-pre2

  A lot has changed since -pre2.

> PS by default in latest CVS, the server logs a lot less to 
> radiusd.log (eg auth OK, auth fail etc - i have logging set to 
> yes int he config but still no output) whats the required
> config change to get the 'old behaviour' back? 

  Hmm... it *should* be configurable in radiusd.conf.  See the "log"
section in radiusd.conf.  Some configuration items have moved, because
it was dumb to have "log_foo", "log_bar", "log_baz", etc.

  Alan DeKok.