[syslog-ng] syslog-ng 1.6.8 bug: not maintaining priority

[Evan Rempel]

If I use the template option for TCP or UDP destinations, the priority of
a message is always user.notice.

I set up a syslog.conf as

source local { unix-dgram("/dev/log"); internal(); };
source network { udp(port(514)); tcp(port(514)); };
destination syslogng { file("/var/log/syslog-ng" template("$DATE $HOST $FACILITY $PRIORITY $MESSAGE\n")); }        ;
destination self { udp("cashmere.comp.uvic.ca" template("$FACILITY $PRIORITY From $HOST: $MESSAGE\n")); };
log { source(local); destination(self); };
log { source(network); destination(syslogng); };

and then I ran
logger -p ftp.alert "everything is wrong"

and I got the following in the /var/log/syslog-ng file

Sep 15 10:38:51 cashmere.comp.uvic.ca user notice ftp alert From cashmere.comp.uvic.ca: sysprog: everything is wrong

Notice that the udp sent message contains the original ftp.alert priority, 
but when the message is received via UDP, the message has priority 
user.notice.

Am I doing something wrong?

--
Evan Rempel				erempel at uvic.ca
Senior Programmer Analyst		250.721.7691
Computing Services
University of Victoria