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@xxxxxxxxxx) 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@xxxxxxxxxx > 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 _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos