[syslog-ng]Entries being logged to /var/log/messages as wellas /var/log/HOSTS//$MONTH/$DAY/$HOS

[Fred Turner]

Sure, it's as follows.=0A=0Adestination debug { file("/var/log/debug"); };=
=0Adestination messages { file("/var/log/messages"); };=0A=0A=0Alog { source=
(src); filter(f_daemon); destination(messages); };=0Alog { source(src); filt=
er(f_kern); destination(messages); };=0Alog { source(src); filter(f_lpr); de=
stination(lpr); };=0Alog { source(src); filter(f_mail); destination(mail); }=
;=0Alog { source(src); filter(f_user); destination(messages); };=0Alog { sou=
rce(src); filter(f_uucp); destination(uucp); };=0Alog { source(src); filter(=
f_mail); destination(maillog); };=0Alog { source(src); filter(f_mail); filte=
r(f_info); destination(mailinfo); };=0Alog { source(src); filter(f_mail); fi=
lter(f_warn); destination(mailwarn); };=0Alog { source(src); filter(f_mail);=
 filter(f_err); destination(mailerr); };=0Alog { source(src); filter(f_news)=
; filter(f_crit); destination(newscrit); };=0Alog { source(src); filter(f_ne=
ws); filter(f_err); destination(newserr); };=0Alog { source(src); filter(f_n=
ews); filter(f_notice); destination(newsnotice); };=0Alog { source(src); fil=
ter(f_messages); destination(messages); };=0Alog { source(src); filter(f_eme=
rgency); destination(console); };=0A=0A=0A=0A=0A>>> Bill Nash <billn@billn.n=
et> 1/29/2005 1:15:26 PM >>>=0A=0ACan you include your log directive? Chance=
s are, that's the culprit.=0A=0A- billn=0A=0A=0AOn Sat, 29 Jan 2005, Fred Tu=
rner wrote:=0A=0A> Hi, I'm new to syslog-ng and have configured it to be a l=
oghost for many different firewall appliances. So I setup an automatic sorti=
ng entry as per the faq as follows:=0A>=0A> destination std {=0A>        fil=
e("/var/log/HOSTS/$MONTH/$DAY/$HOST-$YEAR-$MONTH-$DAY"=0A>                ow=
ner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)=0A>        =
);=0A>=0A>=0A> Which works prefect The only problem is that it's also puttin=
g them in the /var/log/messages log.=0A>=0A> How Can I stop the behavior as =
it's creating a huge /var/log/messages log.=0A>=0A>=0A> Thanks=0A>=0A>=0A> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A>=0A> NOTE: This email an=
d any files transmitted with it are confidential and intended solely for the=
 use of the individual or entity to whom they are addressed. If you have rec=
eived this email in error please notify the sender. Please note that any vie=
ws or opinions presented in this email are solely those of the author and do=
 not necessarily represent those of BBi Enterprises Inc.=0A> Finally, the re=
cipient should check this email and any attachments for the presence of viru=
ses. BBi Enterprises Inc. accepts no liability for any damage caused by any =
virus transmitted by this email.=0A>=0A>=0A> _______________________________=
________________=0A> syslog-ng maillist  -  syslog-ng@lists.balabit.hu =
=0A> https://lists.balabit.hu/mailman/listinfo/syslog-ng =
=0A> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html =
=0A>=0A>=0A_______________________________________________=0Asyslog-ng maill=
ist  -  syslog-ng@lists.balabit.hu =
=0Ahttps://lists.balabit.hu/mailman/listinfo/syslog-ng =
=0AFrequently asked questions at http://www.campin.net/syslog-ng/faq.html =
=0A=0A=0A=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=0ANOTE: This=
 email and any files transmitted with it are confidential and intended solel=
y for the use of the individual or entity to whom they are addressed. If you=
 have received this email in error please notify the sender. Please note tha=
t any views or opinions presented in this email are solely those of the auth=
or and do not necessarily represent those of BBi Enterprises Inc. =
=0AFinally, the recipient should check this email and any attachments for th=
e presence of viruses. BBi Enterprises Inc. accepts no liability for any dam=
age caused by any virus transmitted by this email.=0A