[rsyslog] backward compatibility...

Jakob Haufe sur5r at sur5r.net
Tue Dec 18 22:16:54 CET 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Rainer Gerhards" <rgerhards at hq.adiscon.com> wrote on Mon, 17 Dec 2007
11:04:33 +0100:

> Do you think it would be acceptable to not emit messages in this case,
> slightly breaking backward compatibility? Or should I come up with a
> solution. The later would probably require a specific option setting
> to disable the -m option and its default (somehow telling "I am not
> running in v2 compatibility mode").

This makes me think about sysklogd compatibility. How about the
following: If there's no rsyslog.conf but a syslog.conf then rsyslogd
could go to v2/sysklogd-compatibility mode. If not, it should run in
native mode.
This should improve compatibility in "drop-in replacement for stock
sysklogd" setups.

Regards,
sur5r
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHaDjK1YAhDic+adYRArd6AJ9fXRZU1TnW4L/eKRSfcE3x/G/PMACfbDEF
GgU6vviKYQQofAeAJ9vEnDw=
=6u5b
-----END PGP SIGNATURE-----


More information about the rsyslog mailing list