[lkml]   [2002]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Event logging vs enhancing printk
Michael Holzheu wrote...
> I think it would be important to have both options:
> feed printk messages into posix event logging (this does
> the current patch as far as I know)

The current patch forks the message to evlog inside the printk
function. This thread is proposing that the printk function be
wrapped inside a macro so you could easily capture
file/funcname/lineno of the calling function along with the
original printk message
(plus the other stuff stored in the evlog record header).

> AND feed events
> which are written with the new posix event APIs into the
> traditional syslogd logging.

This would be done in user-space, not in the kernel. This is on
our enhancements list for event logging.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.023 / U:6.852 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site