[syslog-ng] Problem with local*
Javier Terceiro
correolista at gmail.com
Wed Aug 8 11:20:54 CEST 2007
Hello list,
I am forming a system syslog and have a problem with facility's
local*, I have two destinations, the first:
filter f_local7_info {
facility(local7)
and level(info);
};
destination df_local7_info {
file("/var/log/$R_YEAR-$R_MONTH-$R_DAY/$SOURCEIP/$PROGRAM.error.log"
template("$FULLDATE <> $PROGRAM <> $MSGONLY\n")
template_escape(no));
};
log {
source(s_udp);
filter(f_local7_info);
destination(df_local7_info);
};
and the second:
filter f_local6 {
facility(local6);
};
destination df_local6 {
file("/var/log/$R_YEAR-$R_MONTH-$R_DAY/$SOURCEIP/router.log"
template("$FULLDATE <> $PROGRAM <> $MSGONLY\n")
template_escape(no));
};
log {
source(s_udp);
filter(f_local6);
destination(df_local6);
};
The problem is in which some messages with facility local6 are written
in disc with facility local7, reason why does not respect its file.
An example is the following one:
Server:/var/log/10.0.0.51 # ls
239.error.log 241.error.log 244.error.log router.log
Server:/var/log/10.0.0.51 # more 239.error.log
2007 Aug 8 03:30:59 <> 239 -- local6 -- <> *Apr 2 05:15:21:
%LINK-3-UPDOWN: Interface Serial1/1:19, changed state to down
The facility local6 is present in the menssage, but the name of file
is $PROGRAM.error.log
The version of syslog-ng that i use is 1.6.8.
Some idea of so that this happens?
--
Power by Debian.
A greeting,
Javier.
More information about the syslog-ng
mailing list