IGMP Proxy logging makes System logs total mess
Clouseau last edited by
Jan 2 23:50:00 igmpproxy: Note: The IGMP message was from myself. Ignoring.
Jan 2 23:50:00 igmpproxy: Note: RECV V2 member report from 184.108.40.206 to 220.127.116.11 (ip_hl 24, data 8)
Jan 2 23:50:00 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Jan 2 23:50:00 igmpproxy: Note: RECV V3 member report from 18.104.22.168 to 22.214.171.124 (ip_hl 24, data 16)
Jan 2 23:50:00 igmpproxy: Note: RECV V2 member report from 172.30.1.205 to 126.96.36.199 (ip_hl 24, data 8)
How can this noisy application logging be turned off? It's obvious that it works and I don't need any logging for that. This is now messing up all the relevant messages on the log and there for it's also an security and log usability issue. You just don't do any thing with log where 99,99% of the stuff is just from the one working application.
I know that this issue has been up here before, but I must really agree on this. This logging "feature" makes System log unusable! Any relevant idea or workaround to get this fixed?
You could edit /etc/inc/system.inc and edit the function that makes syslog.conf and have it direct those logs to somewhere else (or /dev/null)