Dean Smith wrote: > Ultimately for the same reasons that rlm_detail exists. I'd like to give my > ops guys the ability to see all attributes in requests and replies when > they're debugging or monitoring. We want to maintain all records in a single > SQL database with access via our existing web frontends...so I'd like the > same detail as rlm_detail via the SQl modules.
SQL isn't really the best way to store dozens of lines of text per request. > Obviously many ways to achieve it (parse and upload the detail log, > dedicated perl module etc.) but my scripting/coding is weak so that will > take me longer. rlm_perl, and a special SQL table would likely be best for this. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html