[syslog-ng]syslog-ng 1.5.20

Nate Campi nate@campin.net
Thu, 22 Aug 2002 10:50:36 -0700

On Thu, Aug 22, 2002 at 04:30:51PM +0200, Holtzl Peter wrote:
> Hi,
> New development version of syslog-ng has been released:
> News for the 1.5.20 release
>         Thu, 22 Aug 2002 16:03:45 +0200
>         * fixed a kernel message mangling problem
>         * implemented check_hostname() which checks if a hostname is
>           acceptable (contains characters [0-9a-zA-Z-_.], and if not,
> 	  it is not parsed as hostname, this fixes problems with devices
> 	  which send messages which seem to contain a hostname, but in
> 	  reality they don't


What would be really great is if we could also specify certain strings
which are commonly parsed as hostnames incorrectly. Often messages such
as "Last message repeated 10 times" are parsed as hostname "Last". Some
sites may have a host named "last" so maybe we don't want to globally
decide that "last" is a bad hostname, but if each site could list their
own strings known to *not* be hostnames it could fix some errors.

The $HOST macro would be more usable with this feature. Just today
here's some hostnames incorrectly parsed on my central loghost:

Database (from "Aug 22 10:01:23 Database error: [VENDORLIB] Vendor
Library Error: ct_connect(): network packet layer: internal net library
error: Net-Lib protocol driver call to connect two endpoints failed")

Error (from "Aug 22 10:45:05 Error num: 5")

VendorError1 (from "Aug 22 10:34:12 VendorError1 : 5701")

This means that I get all kinds of bad $HOST macros. Can a feature like
this be implemented?
"Bad Command or File Name. Good try, though."  -Anon. =20
"Press any key... no, no, no, NOT THAT ONE!"  -Anon. =20
"Enter any 11-digit prime number to continue..."  -Anon. =20