Does a log statement need to all be on one line? I have a log statement with two sources, 4 filters and 2 destinations. It all wont fit on one line. When I try to break it up into a block format logging stops for those destiniations. I am sure I am missing something. Here is the log statement: log { source(net); source(net_tcp); filter (f_not_nmrouter); filter (f_not_non_critical_windows); filter (f_not_non_crit_unix); filter (f_not_uiz_servers); destination(x); destination(y); }; Is this broken up correctly? <p class=MsoNormal><span style='font-size:8.5pt'>This e-mail contains Omaha Public Power District's confidential and proprietary information and is for use only by the intended recipient. Unless explicitly stated otherwise, this e-mail is not a contract offer, amendment, nor acceptance. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.</p>
On Tue, 2005-10-18 at 09:00 -0500, SOLIS, ALEX wrote:
Does a log statement need to all be on one line? I have a log statement with two sources, 4 filters and 2 destinations. It all wont fit on one line. When I try to break it up into a block format logging stops for those destiniations.
I am sure I am missing something. Here is the log statement:
log { source(net); source(net_tcp); filter (f_not_nmrouter); filter (f_not_non_critical_windows); filter (f_not_non_crit_unix); filter (f_not_uiz_servers); destination(x); destination(y); };
syslog-ng does not really care about the indentation/whitespace used in configuration files. you can break it to several lines at will. -- Bazsi
On Tue, Oct 18, 2005 at 09:00:54AM -0500, SOLIS, ALEX wrote:
Does a log statement need to all be on one line? I have a log statement with two sources, 4 filters and 2 destinations. It all wont fit on one line. When I try to break it up into a block format logging stops for those destiniations.
I am sure I am missing something. Here is the log statement:
log { source(net); source(net_tcp); filter (f_not_nmrouter); filter (f_not_non_critical_windows); filter (f_not_non_crit_unix); filter (f_not_uiz_servers); destination(x); destination(y); };
Is this broken up correctly?
Looks ok. Send your whole config file, assuming it's under a couple hundred lines. Maybe we'll be able to see it then. OBTW, you sure syslog-ng is running at all when you break it up? You can always invoke syslog-ng with the syntax-only flag: # /sbin/syslog-ng -s -f /tmp/syslog-ng.conf.sunos syntax error at 37 Parse error reading configuration file, exiting. (line 37) In this case I purposely removed a semicolon so you'd see that it tells you where it had trouble. As is typical with syntax problems, it reported the line where it could tell you need a semicolon *before it*: filter f_mail { facility(mail); } filter f_not_mail { not facility(mail); }; In this case line 37 is the "filter f_not_mail" line, the semicolon was needed on the line above. -- Nate "If Microsoft can change and compete on quality, I've won." -- L. Torvalds
participants (3)
-
Balazs Scheidler
-
Nate Campi
-
SOLIS, ALEX