Hi, could it be that PowerDNS sets the error levels on syslog entries a bit strangely? I see messages declared as "error" like the following:
Our pdns instance exited with code 0 Respawning Guardian is launching an instance UDP server bound to ##.##.##.##:53 UDPv6 server bound to [####:####:####::####]:53 TCP server bound to ##.##.##.##:53 TCPv6 server bound to [####:####:####::####]:53 DNS Proxy launched, local port 32275, remote 127.0.0.1:5300 Creating backend connection for TCP Master/slave communicator launching I wouldn't expect to see all those declared as errors, more as notices or something. This requires defining a lot of stupid exceptions to syslog error analysis rules. In fact PowerDNS and its recursor don't seem to ever use any other priorities than Warning and Error. PowerDNS 2.9.22 on Ubuntu 10.04. -- Yves Goergen "LonelyPixel" <nospam.l...@unclassified.de> Visit my web laboratory at http://beta.unclassified.de _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users