Brian A. Seklecki wrote: > Another solution would be to perform logging via syslog(3), which > absolves radiusd from trapping and handling signals and file handlers. > Syslog-ng already does this very well -- why duplicate all of that code?
As always, patches are welcome. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
