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
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
Hi,
Is there a way of using either rlm_sql_log or the post-auth query within
rlm_sql to log all the request and/or reply attributes to mysql ?
as part of our PERL bit of handling we spew out all of the attributes to
a debug log when we want ('if file exists' logic to turn it off and on)
you
I guess I'm asking is there an unlang equivalent to this snippet from
rlm_detail.c. ..
/* Write each attribute/value to the log file */
for (pair = packet-vps; pair != NULL; pair = pair-next) {
vp_print(outfp, pair);
}
Dean
Dean Smith wrote:
I guess I’m asking is there an unlang equivalent to this snippet from
rlm_detail.c. ..
No.
I don't see why it makes sense to log all of the attributes as one big
line of text in SQL. If you need that, it shouldn't be hard to write a
Perl plugin that does it.
Alan
5 matches
Mail list logo