Re: klogd and dmesg behavior

Keith Owens (kaos@ocs.com.au)
Tue, 06 Oct 1998 23:35:17 +1000

On Tue, 6 Oct 1998 05:10:15 -0500,
greg@wind.enjellic.com (G.W. Wettstein) wrote:
>On Oct 5, 12:20pm, by-tor@by-tor.dyn.ml.org wrote:
>> Upon boot of 2.1.124 I no longer have klogd logging the initial bootup
>> sequence messages into syslog, but dmesg correctly reports them. Have the
>> logging semantics changed in some way? Anyone else seeing this problem?
>
>Not that I know of. I am running a 2.1.124 machine here and klogd is
>logging the startup messages just fine.
>
>If anyone else is noticing a problem I would like to know about.

klogd from Redhat sysklogd-1.3-19 gets SEGV on 2.1.123, glibc.

216 time([907678616]) = 907678616
216 write(1, "<4>Oct 6 22:56:56 kernel: RAM d"..., 84) = 84
216 time([907678616]) = 907678616
216 write(1, "<4>Oct 6 22:56:56 kernel: PIIX3"..., 70) = 70
216 time([907678616]) = 907678616
216 --- SIGSEGV (Segmentation fault) ---

The relevant lines in dmesg are

RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX3: IDE controller on PCI bus 00 dev 09
PIIX3: not 100% native mode: will probe irqs later

klogd does not like '%' in messages. Don't know if this has been fixed
in later releases of klogd, redhat 5.1 has 1.3-22.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/