colleague today asked how to have the original syslogd be able to segregate kernel messages based on something like the module name or subsystem and, as far as i know, there's no way to do that. of the original syslog facilities, one of them is "kern", which handles *all* kernel messages, and from that, you can configure with syslog.conf based on the eight possible priorities -- debug, info, notice, warn and so on. so as far as i know, the best you can do is partition kernel messages into at most eight subsets of messages if you wanted -- there is nothing i can see in the original syslog that supports somehow selecting kernel messages based on anything but that. now, i realize that you can embed identifiers in the kernel string being printed, or use the variations dev_notice, dev_warn and so on, to automatically embed the device name in the message, but that still means nothing more than you would still need to grep the final output for the device or module name you were interested in. am i missing anything here? short of moving up to syslog-ng, i see no way that the original syslog can select at the device driver or module level when redirecting kernel messages. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca/dokuwiki Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org To visit the archives: https://lists.linux-ottawa.org