On 03/08/2011 09:46 PM, Stefan Certic wrote:
Hi Sebastian,
Thanks for response. Problem with another log file is that solution is
doubling number of I/O transactions. At some point, data needs to be
phrased into database and written to disk. I'm afraid doubling
operations will cause bottlenecks
Hi Sebastian,
Thanks for response. Problem with another log file is that solution is doubling
number of I/O transactions. At some point, data needs to be phrased into
database and written to disk. I'm afraid doubling operations will cause
bottlenecks during high load traffic peaks and slow-down
Hello,
Configuration:
Bind9 configured to write logs into sys/rsyslog. - From there, data is getting
phrased and used for analytical / billing purposes.
Scenario:
At some point, a problem arise and rsyslog crashes for any possible reason.
There is no unix logging socket any more bind can comm
3 matches
Mail list logo