Messages in this thread | | | From | Denis Vlasenko <> | Subject | Re: How to enable printk | Date | Tue, 30 Apr 2002 16:03:08 -0200 |
| |
On 30 April 2002 10:55, David Woodhouse wrote: > vda@port.imtp.ilyichevsk.odessa.ua said: > > It is not silly as long as kernel continues to log tons of normal > > stuff as warnings. > > Er, IMO it _is_ silly as long as the kernel continues to log real warnings > as warnings too. > > > Here it is: There are way too many printks without a log level! -- > > Oh, well the answer is obvious - just disable _all_ the warning messages. > > Why not turn off KERN_CRIT too, while we're at it? I'm sure we can find at > least one superfluous KERN_CRIT message.
Hey, hey... do you expect users to patch all those printk() calls in their kernel themself? Realistically they can:
* enable console logging for warnings and be flooded * disable console logging for warnings and stay blind * send patches to lkml and be ignored * configure syslogd to print warnings on a dedicated tty
Anyway, that's what I did. -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |