[BusyBox] older 06.5 syslogd problem

[Brian T]

----- Original Message ----- 
From: "Brian T" <btuch at usa.net>
To: "Larry Doolittle" <ldoolitt at recycle.lbl.gov>; <busybox at mail.busybox.net>
Sent: Tuesday, January 27, 2004 4:46 PM
Subject: Re: [BusyBox] older 06.5 syslogd problem


>
> > >
> > > > I was wondering if anyone has seen the older busybox syslogd remove
> the
> > > > "<" character, and the next character after it when looking at the
> 60.5
> > > > syslogd version?
> > >
> > > This looks like syslog is interpreting these entries as if they were
> coming
> > > from kernel printk output via klogd and interpreting the <? character
> > > sequences as log levels.  The kernel log levels are indicated by using
> > > special character strings at the front of log messages like "<0>",
"<1>"
> > > etc.  They are defined in linux/kernel.h as macros KERN_EMERG,
> KERN_ALERT
> > > etc.
> > >
> > > I suspect it should only be accepting them at the start of the
message,
> and
> > > only if they match the pattern '<' digit 0-7 '>'.
> >
> > I agree entirely.  The only flaw I see in the analysis is that the
> > code I see in busybox-0.60.5 klogd.c (that Gennady Feldman wrote and
> > I helped test, years ago) appears to do exactly that.  Is there a
> > chance Brian has an older busybox around, or a non-busybox klogd
running?
> >
> >     - Larry
>
> I'm running busybox 0.60.5.  Both klogd and syslogd are from this version
> I'm running :
>
> [root at JBMgateway-v59 root]# ps ax
>   PID TTY      STAT   TIME COMMAND
>     1 ?        S      0:05 init
>   252 ?        S      0:00 /sbin/syslogd -n
>   253 ?        S      0:00 /sbin/klogd -n
>   255 ?        S      0:00 /bin/inetd
>   256 ttyS0    S      0:00 -sh
>   319 ttyS0    R      0:00 ps ax
> [root at JBMgateway-v59 root]# ls -al /sbin/klogd
> lrwxrwxrwx    1 root     root           14 Jan 27 14:33 /sbin/klogd ->
> ../bin/busybox
> [root at JBMgateway-v59 root]# ls -al /sbin/syslogd
> lrwxrwxrwx    1 root     root           14 Jan 27 14:33 /sbin/syslogd ->
> ../bin/busybox
> [root at JBMgateway-v59 root]# busybox
> BusyBox v0.60.5 (2004.01.13-16:18+0000) multi-call binary
>
> What do you suggest?
>
> -Brian
>
>

I guess I'll rewrite this for myself, and release the code. What's a good
place to start at in the Log message to start looking for the Priority
<0-9>? Pointer 1? 2? 3?

Thanks,

-Brian