[kde-linux] [Bulk] Konsole Immunity Lost

James Tyrer jrtyrer at earthlink.net
Thu Sep 24 23:07:52 UTC 2009


David Baron wrote:
> On Sunday 06 September 2009 17:56:01 David Baron wrote:
>> On Sunday 06 September 2009 16:55:15 David Baron wrote:
>>> On Saturday 05 September 2009 22:11:52 David Baron wrote:
>>>>>> I never had them before in konsole or yakuake--all those syslogd
>>>>>> messages  about various internet packets aborted, i.e. by firewall
>>>>>> or fail2ban. With the latest and greatest 4.3.1, now I get them.
>>>>>>
>>>>>> I really do not want them as they make the console almost unusable.
>>>>>> So how do  I get rid of them?
>>>>> You can control this by setting:
>>>>>
>>>>> /proc/sys/kernel/printk
>>>>>
>>>>> My system has this set to 3 4 1 7 and I had to read the manual
>>>>> (manpages proc and syslog) to know what that means.  I think that it
>>>>> is the first number that you need to change.  A lower number means
>>>>> less messages.
>>>>>
>>>>> You can see what your system is currently set at with (as root):
>>>>>
>>>>> cat /proc/sys/kernel/printk
>>>>>
>>>>> and then set it with:
>>>>>
>>>>> echo "3 4 1 7" > /proc/sys/kernel/printk
>>>>>
>>>>> To permanently change this, edit:
>>>>>
>>>>> /etc/sysctl.conf
>>>> The first few lines in this file have instructions on what to do here.
>>>>
>>>> Does not explain why I never got them before in konsole/yakuake. But I
>>>> do not mind getting rid of them in "real" consoles as well.
>>> I did it. Now I no only get them in yakuake but they showup as writed
>>> bulletins on the desktop as well! I will try the 4 4 1 7 recommended in
>>> the file and see what happens.
>> Still getting them but not on desktop. Of course, there MAY be fewer of
>>  them, no way of telling.
>>
> This problem remains with 3 4 1 7, 4 4 1 7 or the line commented.
> With the recommended 4 4 1 7, a session with a konsole, i.e. yakuake, will 
> have the messages flooding that. If the session has no konsole, the they 
> appear a kwrited message on the desktop. In all, a royal pain.

Changes to the file will only take effect after a reboot.  To change a
running Kernel, you need to (as root):

	echo "3 4 1 7" > /proc/sys/kernel/printk

-- 
James Tyrer

Linux (mostly) From Scratch



More information about the kde-linux mailing list