On Tue, Feb 05, 2008 at 08:57:32AM +0900, Peter F Bradshaw wrote:
> Hi;
>
> I have a Debian kernel in which some printks have been left. These make
> a mess of the console and logs. Is there any way, other than recompiling
> the kernel, of suppressing the printk output?
Another method, in case yo
Further searching resulted in this message:
http://lists.debian.org/debian-user/2007/03/msg01554.html
of which this snippet is key:
The settings in /etc/sysctl.conf take effect at the next reboot. You can
change the printk setting with immediate effect with
echo "4 1 1 7" > /proc/sys/kernel/pr
* Peter F Bradshaw <[EMAIL PROTECTED]> [2008 Feb 04 18:15 -0600]:
> Hi;
>
> I have a Debian kernel in which some printks have been left. These make
> a mess of the console and logs. Is there any way, other than recompiling
> the kernel, of suppressing the printk output?
Did you uncomment the foll
On Feb 4, 2008 6:57 PM, Peter F Bradshaw <[EMAIL PROTECTED]> wrote:
> Hi;
>
> I have a Debian kernel in which some printks have been left. These make
> a mess of the console and logs. Is there any way, other than recompiling
> the kernel, of suppressing the printk output?
I think there is a "quiet
Hi;
I have a Debian kernel in which some printks have been left. These make
a mess of the console and logs. Is there any way, other than recompiling
the kernel, of suppressing the printk output?
Thanks.
Cheers
--
Peter F Bradshaw: http://www.exadios.com (public keys avaliable there).
Personal
5 matches
Mail list logo