: Log and console pollution: ip_tables: (C) 2000-2002 Netfilter core team
Hi All,
I notice anoying messages in logs and on the console such as the above.
Gladly, most humble authors refrain from this bloat.
Could one ban these messages from the console altogether and perhaps mandate sending credits to a seperate "credits log" file
Regards
Michael Frank
Hi,
Quoted 1 line
Gladly, most humble authors refrain from this bloat.
Strange, i though we are coding for fame and glory ? :)
But seriously...
You see these messages only when you load the module. On a non-testbed-machine it is once a boot. I would not call that polluting the logs.
On the other hand on a testbed-machine you see these messages when you load and reload the modules. I treat these messages as debug messages. When I develop a module i put versioning info there, and i know if I loaded the correct module or some previous version.
Regards,
Maciej Soltysiak
-----BEGIN GEEK CODE BLOCK-----
VERSION: 3.1
GIT/MU d-- s:- a-- C++ UL++++$ P L++++ E- W- N- K- w--- O! M- V- PS+ PE++ Y+ PGP- t+ 5-- X+ R tv- b DI+ D---- G e++>+++ h! y?
-----END GEEK CODE BLOCK-----
Quoted 5 lines · Michael Frank
Hi All,
I notice anoying messages in logs and on the console such as the above.
Gladly, most humble authors refrain from this bloat.
Well, it is not any more bloat than printing a line like 'ip_tables:
initialized ip_tables core successfully'.
Quoted 2 lines
Could one ban these messages from the console altogether and perhaps mandate sending credits to a seperate "credits log" file
I remember a huge discussion on this subject quite some time (years?) ago on lkml, so don't let's repeat a flame war about this.
Quoted 2 lines
Regards
Michael Frank
Signature · 5 lines
- Harald Welte <[email protected]> http://www.netfilter.org/ ============================================================================ "Fragmentation is like classful addressing -- an interesting early architectural error that shows how much experimentation was going on while IP was being designed." -- Paul Vixie