Jobst Schmalenbach
2017-Aug-02 03:32 UTC
[CentOS] Problem with IPTABLES logging message to the screen/console
Hi I am not sure how to solve this. I am constantly getting messages that should go into the kern/message log printed on screen - MOSTLY from iptables. The messages are ALSO logged to the syslog files. It still prints those message onto the console screen even if I am logged off (security issue). When logged in on the console its anoying as I constantly have to hit CTRL-L to refresh the screen to get rid of those messages. However it does NOT happen when I ssh into the machine. How can I solve this that those messages are NOT printed. thanks Jobst -- Share your knowledge. It's a way to achieve immortality. | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
Anthony K
2017-Aug-06 10:03 UTC
[CentOS] Problem with IPTABLES logging message to the screen/console
On 02/08/17 13:32, Jobst Schmalenbach wrote:> How can I solve this that those messages are NOT printed.I think you are after *dmesg -n alert* man dmesg ... -n, --console-level level Set the level at which printing of messages is done to the con? sole. The level is a level number or abbreviation of the level name. For all supported levels see the --help output. For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so sys? logd(8) can still be used to control exactly where kernel mes? sages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. ...
Jobst Schmalenbach
2017-Sep-05 02:17 UTC
[CentOS] Problem with IPTABLES logging message to the screen/console
Thanks, that fixed it! It seems it need to go into rc.local, it gets wiped after a reboot due to kernel updates. Jobst On Sun, Aug 06, 2017 at 08:03:53PM +1000, Anthony K (akcentos at anroet.com) wrote:> On 02/08/17 13:32, Jobst Schmalenbach wrote: > > How can I solve this that those messages are NOT printed. > I think you are after *dmesg -n alert* > > man dmesg > ... > -n, --console-level level > Set the level at which printing of messages is done to the > con??? > sole. The level is a level number or abbreviation of the > level > name. For all supported levels see the --help output. > > For example, -n 1 or -n alert prevents all messages, > except > emergency (panic) messages, from appearing on the console. > All > levels of messages are still written to /proc/kmsg, so > sys??? > logd(8) can still be used to control exactly where kernel > mes??? > sages appear. When the -n option is used, dmesg will not > print > or clear the kernel ring buffer. > ... > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos-- 186,262 miles/second : Not just a good idea, it's the LAW. | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia
Possibly Parallel Threads
- CentOS 6.X, iptables 1.47 and GeoLite2 Country Database
- sendmail, port 465/587, auth and imap
- CentOS 6.X, iptables 1.47 and GeoLite2 Country Database
- What files to edit when changing the sdX of hard drives?
- CentOS 6.X, iptables 1.47 and GeoLite2 Country Database