On Feb 14, 2006, at 10:47 AM, DAve wrote:
Daniel Cañas Montero wrote:
On Feb 11, 2006, at 3:14 PM, Ed Russell wrote:
I have to say a heartfelt THANK YOU to everyone who contributed
to this
thread. My filter is working 500% more efficient that it ever
was. I have
done the following:
1. Installed djbdns and I am using dnscache as I was told. I
have
increased the cache size to 100 Megabytes and completely
disabled logging
after determining it was working properly.
How do you disable logging completely? I use multilog and filter
out all the lines so it logs nothing.
Is there a way to tell dnscache not to actually spit anything out?
Only by removing code from dsncache I believe. Most people just
limit what, if anything, is picked up by multilog. I've never tried
it but it would be interesting to see what
#svc -d /service/dnscache/log
would do. That would remove any need to modify your log/run script.
I know some people just redirect dnscache output to /dev/null. I
sometimes need to see what the stats are for dnscache when checking
SA (URIBL SURBL), so I've never done it.
DAve
OK. That is what I do currently...have '-*' in my multilog....
but I thought there might be a way to avoid having a 'dummy' multilog
process running.
I have l aso tried not starting the multilog (ie #svc -d /service/
dnscache/log), and it seems to work... but I wasn't sure if it would
do anything funny over the long run, so I started it up again.
Maybe this is a dumb question...
But is it ok to have a process monitored by supervise not to have a
corresponding multilog running to capture the output?
