Date: Fri, 25 Aug 2000 18:36:23 +0200

Hi Sascha,

I will extend the regexp support in the next version insofar, as it will =

be

possible to extract substrings of the message text for logging purposes. =

I

will consider throwing in a search/replace feature, but I can't make any

promise yet.

Franz

"Sascha Mettler" <sascha.mettler@bern.ch> wrote in message

news:3A25DBCDF73F2245957BD0B041BEDAF001657A@is1.netal.com...

> Eric Rodziewicz schrieb in Nachricht

> <3A25DBCDF73F2245957BD0B041BEDAF001655F@is1.netal.com>...

> >

> > I do exactly that with triggers in the database I send the data =

into.

> >It is my "gateway to Syslog".

>

> >

> > I have very verbose notification/forwarding rules based on

information

> >in a different database.

> >

> > I think a Syslog Daemon should log and transport well, but leave =

the

> >parsing of domain specific messages to other domain specific

applications.

>

> Your solution sounds great but I'm sure there are people who don't =

wan't

to

> (or aren't able to) manage a database-server with triggers etc. At =

least I

> don't.

> Furthermore, you loose the "actions" of sl4nt and have to implement =

them

all

> by

> yourself. I think sl4nt is a great product and i try to use a much of =

its

> functionality

> as possible. All I added until today is a country specific =

sms-software to

> send

> some of the messages to my mobile phone.

>

> On the other hand I agree that a syslog daemon should be small and =

simple

so

> how

> about my idea of a preprocessor interface. the message-text should be

> reroutable via

> an external program/script which would return it after selective

> string-manipulations.

> that would only add one checkbox and one script-selection to the whole

> system. Of

> course from the user point of view, I'm not talking about the =

necessary

> programming 😉.

>

>

>

> my 2 ct.

>

> greetings from Switzerland

> Sascha

>

>

>