On Sat, 14.05.11 12:01, Philip A. Prindeville (philipp_s...@redfish-solutions.com) wrote:
> May 13 11:08:02 mail kernel: [ 133.097131] sendmail[2179]: p4DH6ui4002179: > Milter delete (noop): header: X-Spam-Score > May 13 11:08:02 mail kernel: [ 133.105238] sendmail[2179]: p4DH6ui4002179: > Milter add: header: X-Scanned-By: MIMEDefang 2.72 on 192.168.1.3 > May 13 11:08:02 mail kernel: [ 133.115242] lmtpunix[2176]: accepted > connection > May 13 11:08:02 mail kernel: [ 133.119932] lmtpunix[2176]: lmtp connection > preauth'd as postman > May 13 11:08:02 mail kernel: [ 133.884189] lmtpunix[2176]: skiplist: > checkpointed /var/lib/imap/user/p/philipp.seen (387 records, 116172 bytes) in > 0 seconds > May 13 11:08:02 mail kernel: [ 133.895967] lmtpunix[2176]: seen_db: user > philipp opened /var/lib/imap/user/p/philipp.seen > May 13 11:08:02 mail kernel: [ 188.010336] master[1892]: process 2170 > exited, status 0 > May 13 11:08:02 mail kernel: [ 188.016042] master[2204]: about to exec > /usr/lib/cyrus-imapd/lmtpd > May 13 11:08:02 mail kernel: [ 188.022558] lmtpunix[2204]: executed > > so it looks like mail messages are being relogged as kernel messages???? > What's going on? systemd provides logging from beginning of userspace on. As long as syslog isn't up this will go to kmsg. As soon as rsyslog is up the kernel log buffer will be fliushed to disk and all following messages go directly to disk with no involvement of kmsg. In F16 and later you'll be able to use "dmesg -k" to get the usual dmesg output but with all non-kernel messages removed. Note that dmesg never has been about kernel messages only. Low-level userspace system components logged to kmsg already. All we added is that during early boot /dev/log logging ends up in kmsg. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
