(was latest CVS 2.0) - logging issue
A.L.M.Buxey at lboro.ac.uk
A.L.M.Buxey at lboro.ac.uk
Fri Jan 4 21:50:01 CET 2008
Hi,
> A lot has changed since -pre2.
>
> 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.
ha! a lot HAS been changing. damn. you are right. how did
i miss that fundamental change to the log {} section. ???
crazy. anyway, i have now moved all the pre-2 log stuff log_auth,
log_file etc etc into the correct single log {} stanza and removed
the legacy log_ prefix which each entry had. its all working fine
now.
there was another post by someone else on this list a while back
about latest CVS being more quiet than the old. perhaps this needs
to be highlighted a little better - perhaps have somehting in the
startup parser that can detect these old legacy configs and spew
out a warning? in 'the old days' the log_ entries could lie
anywhere in radiusd.conf - really should only be in log {}
and no entries should start with log_ ...... ah! but they do. we have
a small oddity
log_destination = files
surely this should also be cleared into the log {} stanza? eg
log {
destination = files
}
sorry for the false alert and thanks for the pointer/tip to getting
this little issue sorted.
alan
More information about the Freeradius-Users
mailing list