[BusyBox] older 06.5 syslogd problem

[Stewart Brodie]

"Brian T" <btuch at usa.net> wrote:

> Hi,
> 
> 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?  I see it alot with pppd debugging turned on.  Sorry if
> this has been addressed already.  If someone knows the fix for this it
> would be greatly appreciated.
> 
> Exalmple:
> 
> Jan 27 10:33:26 pppd[6209]: rcvd [LCP ConfReq id=0x29 ru 1514> syncmap
0x0> agic 0xa6bb9500> comp> ccomp>]
> 
> shoulld look like:
> 
> Jan 27 10:33:26 pppd[6209]: rcvd [LCP ConfReq id=0x29 <mru 1514> <asyncmap
0x0> <magic 0xa6bb9500> <?comp> <?ccomp>]

I can't help with a fix, but I can suggest a possible cause.

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 '>'.

-- 
Stewart Brodie