Title: Acipia
Paolo Lucente a crit:
Hi Denis,
sorry for the late reply. You really have two options:
No problem, i'm also a really busy man !
- you can tag traffic through the Pre-Tagging infrastructure as you
were suggesting. Then, you can select it on a per-plugin basis with
Hello Paolo!
Sorry again but i found something strange in 'pmacct' behaviour.
I have follow setting for history saving on my 'nfacctd':
! nfacctd_time_secs: true
! nfacctd_time_new: true
sql_refresh_time: 120
sql_history: 1d
sql_history_roundoff: h
But i see next records in my
I want to supplement my previous letter that my problem not
limited only 'tcp' protocol:
bytes ip_proto stamp_inserted stamp_updated
2188048tcp 2008-04-17 00:00:00 2008-04-18 11:28:01
538793udp 2008-04-17 00:00:00 2008-04-18 09:56:01
alex a crit :
Hello Paolo!
Sorry again but i found something strange in 'pmacct' behaviour.
I have follow setting for history saving on my 'nfacctd':
! nfacctd_time_secs: true
! nfacctd_time_new: true
sql_refresh_time: 120
sql_history: 1d
sql_history_roundoff: h
But i see
Hello Paolo!
Sorry again but i found something strange in 'pmacct' behaviour.
I have follow setting for history saving on my 'nfacctd':
! nfacctd_time_secs: true
! nfacctd_time_new: true
sql_refresh_time: 120
sql_history: 1d
sql_history_roundoff: h
But i see next
Hi Rene,
it smells like the MySQL plugin writer process is unable to write
down all the tuples by the time in which a new writer is spawned.
This should reveal an non-optimal setting of either aggregate or
sql_refresh_time directives. This is easily caused by either the
specs of the box on
