Hi Jaroslav,
Unfortunately not as they are integral part of the sql_history feature
(which you need to populate the time-related variables of the tables).
As an alternative, only for the 'all' tables where you have the other
timestamps, you may disable sql_history and write to a fixed, say,
Hi, I use this scerario:
sql_refresh_time: 120
sql_history: 2m
sql_history_roundoff: m
sql_dont_try_update: true
nfacctd_pro_rating: true
aggregate[router1.all.in]:
src_host,dst_host,proto,src_port,dst_port,timestamp_start,timestamp_end
aggregate[router1.all.out]:
Hello Jamie,
On Tue, Aug 16, 2005 at 05:07:33PM +1000, Jamie Wilkinson wrote:
Actually, I'm still not clear: the FAQ suggests that only sql_history is
required, though sql_history_roundoff is advised. Is that true?
True. sql_history writes the stamp fields; sql_history_roundoff enables the
This one time, at band camp, Paolo Lucente wrote:
On Sat, Aug 13, 2005 at 02:14:00AM +1000, Jamie Wilkinson wrote:
Ok. Does this mean that unless the config options 'sql_history' and
'sql_history_roundoff' exist, then pmacctd will not write time stamps to the
database?
yes.
Thanks for the
On Sat, Aug 13, 2005 at 02:14:00AM +1000, Jamie Wilkinson wrote:
Ok. Does this mean that unless the config options 'sql_history' and
'sql_history_roundoff' exist, then pmacctd will not write time stamps to the
database?
yes.
I've done so, but I've also added these two config options back
