Garbled syslog

[Jon Lapp]

Has anyone ever seen anything like this before? Where should I start?
SCO Openserver 5.0.2 Enterprise with:

oss449f
oss458a
oss468a
oss601a

-----<Start garbled mess>-----

WARNING: table_alloc - Failed to get address space for exec data table
Thu Feb 21 16:59:59 2002
CCPPUU43::

CCCPPPUUU423::: W
WACARPRNUNI2IN:NG G:W: A RtNtaIabNblGle:e_ _aaltllaloboclc e -_- a
FlFalaioilcle
ed-d tFtoao i glgeeetdt atadodd drgreeestss s a sdspdparacecese s f
fosorpr
a ecexexe ecfc o drda atetaxa e tcta abdblaletea

table
CPU2:
CPU2: WARNING: table_alloc - Failed to get address sCpPaUc3e: f
oCrP Ue3x:e cW AdRaNtIaN Gt:a blteab
le_alloc - Failed to get address space for exec data table

WARNING: table_alloc - Failed to get address space for exec data table
Thu Feb 21 16:59:59 2002
CPU3:
CPU3: WARNING: table_alloc - Failed to get address space for exec data table
CPU3:
CPU3: WARNING: table_alloc - Failed to get address space for exec data table

-----<End garbled mess>-----

TIA

Jon

[Stuart J. Browne]

"Jon Lapp" <la...@nsff.com> wrote in message
news:3c758...@news.teranews.com...

Yeap, seen this before. It actually makes sense if you just go back and
read it again..
CCPPUU43::
CCCPPPUUU423::: ..>

CPU4:
CPU3:
CPU4: WARNING: table_alloc - Failed to get address space for exec data table
CPU2:

CPU3: WARNING: table_alloc - Failed to get address space for exec data table

CPU2: WARNING: table_alloc - Failed to get address space for exec data table

All that happened is that all 3 processes hit Syslog at the same time. If
you take the time to dissasemble the messages, you'll figure out what it
says.

I've seen this before on SMP systems using 5.0.5 and 5.0.4.

I wouldn't be too worried. Is anybody aware of a syslog fix to handle
multiple executions/logger calls simultaneiously?

bkx