[PATCH] value-pairs: Use MESSAGE instead of MSG.
MESSAGE is the canonical name of the key, not MSG. Using MSG in the rfc3164 scope will result in both MSG and MESSAGE being present if nv-pairs is being used aswell. Using the canonical name, only MESSAGE will end up in the set, which is exactly what we'd like. Signed-off-by: Gergely Nagy <algernon@balabit.hu> --- lib/value-pairs.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/value-pairs.c b/lib/value-pairs.c index f88a486..7a09812 100644 --- a/lib/value-pairs.c +++ b/lib/value-pairs.c @@ -76,7 +76,7 @@ static ValuePairSpec rfc3164[] = { "HOST" }, { "PROGRAM" }, { "PID" }, - { "MSG" }, + { "MESSAGE" }, { "DATE", "R_DATE" }, { 0 }, }; -- 1.7.2.5
On Sun, 2011-05-08 at 10:37 +0200, Gergely Nagy wrote:
MESSAGE is the canonical name of the key, not MSG. Using MSG in the rfc3164 scope will result in both MSG and MESSAGE being present if nv-pairs is being used aswell.
Using the canonical name, only MESSAGE will end up in the set, which is exactly what we'd like.
Signed-off-by: Gergely Nagy <algernon@balabit.hu>
Thanks, applied. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Gergely Nagy