Hi Indeed - there is (although I haven't tested it yet for ippools) the option at top level. I was trying (if possible) to only log the ippool queries rather than everything - However I can look at this for now and grep/etc the queries needed On Thursday 04/07/2019 at 10:52 pm, Arran Cudbard-Bell wrote:
On 4 Jul 2019, at 15:50, Richard J Palmer <richard@merula.net> wrote:
Hi All
I am trying to optimize some SQL queries & Database performance here - particularly for iptables
Now for accounting I can have something like:
accounting { # Write SQL queries to a logfile. This is potentially useful for bulk inserts # when used with the rlm_sql_null driver. logfile = ${logdir}/accounting.sql
I have tried adding that inside the iptables query file - but that file does not seem to allow that.
Is there any way to log just the queries from the SQL IP Pool module ?
rlm_sql.c says there's a top level logfile config item, which'd presumably log requests sent from the ippool module.
e.g.:
sql { logfile = "<path>" }
I think the ippool module calls a function which respects that logfile, if it doesn't, report back and someone will fix it for 3.0.20.
Thanks, -Arran
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 4 Jul 2019, at 17:55, Richard J Palmer <richard@merula.net> wrote:
Hi
Indeed - there is (although I haven't tested it yet for ippools) the option at top level.
I was trying (if possible) to only log the ippool queries rather than everything - However I can look at this for now and grep/etc the queries
Use multiple instances of the sql module. If you care about the additional connections, share the connection pool. If you care about config duplication, use templates. -Arran
participants (2)
-
Arran Cudbard-Bell -
Richard J Palmer