[syslog-ng] log_fifo_size and locked tables
Rob Munsch
rmunsch at solutionsforprogress.com
Tue Apr 11 21:55:20 CEST 2006
'allo all,
I've 1.6.9 in a centralized environment logging to MySQL.
I'm currently working up a rotate system whereby:
- the db is locked
- mysqldump, gzip, scp off the box
- rows with a timestamp older than 7 days are deleted
- unlock
- carry on.
and was wondering a couple things. Firstly,
1) is this a horribly bad idea that should be replaced with a completely
different plan?
failing that,
2) How long does the default log_fifo_size of 2048 (lines, yes?) hold
up, volume-wise? That is, while the tables are locked, i am assuming
that this is where messages start piling up until they're unlocked. At
the moment, i'm not dealing with high volume, but once everything seems
in place i'm going to be adding many more hosts.
is there any kind of rule of thumb for this value vis-a-vis the logs
generated? At what sort of daily volume should i look towards upping it?
Thanks!
--
Rob Munsch
Solutions For Progress IT
More information about the syslog-ng
mailing list