Date: Thu, 5 Jul 2001 09:02:46 -0700

Hi,

Currently we are using SLANT as our Syslog Daemon and allowing our messages

to be forwarded to a log to be parsed into Netcool. We are using a perl

scrip supplied by your company to parse the data and it works great, to a

point. I am beginning to notice that as the day goes on, our messages are

backing up and we experience a ever growing latency as to the time the

Syslog message is reported, and the time it shows in Netcool. After

reviewing the logs everything is fine and the times match, until it hits the

perl script.

Any Ideas as to why this might be happening, or how to fix ?

Jay at MS

Date: Thu, 5 Jul 2001 22:22:23 +0200

Hi Jay,

>We are using a perl

> scrip supplied by your company to parse the data and it works great

this script was not supplied by us, it must be the product of an internal MS

guy (maybe Jeremy Doig?).

Franz

"Jay Witcher" <switcher@microsoft.com> wrote in message

news:#KxkZwWBBHA.2652@is1.netal.com...

> Hi,

>

> Currently we are using SLANT as our Syslog Daemon and allowing our

messages

> to be forwarded to a log to be parsed into Netcool. We are using a perl

> scrip supplied by your company to parse the data and it works great, to a

> point. I am beginning to notice that as the day goes on, our messages are

> backing up and we experience a ever growing latency as to the time the

> Syslog message is reported, and the time it shows in Netcool. After

> reviewing the logs everything is fine and the times match, until it hits

the

> perl script.

>

> Any Ideas as to why this might be happening, or how to fix ?

>

> Jay at MS

>

>

>