holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Enhance answer to Shorewall FAQ 16a

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5181 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-01-01 23:33:28 +00:00
parent a0b42400a3
commit 277cd2b3d4
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/FAQ.xml
View File

@ -1023,12 +1023,24 @@ DROP net fw udp 10619</programlisting>
<title>(FAQ 16a) Why can't I see any Shorewall messages in <title>(FAQ 16a) Why can't I see any Shorewall messages in
/var/log/messages?</title> /var/log/messages?</title>
<para><emphasis role="bold">Answer:</emphasis> The actual log file <para><emphasis role="bold">Answer:</emphasis> First of all, it is
name will likely not be well standardized, but anytime you see no important to understand that Shorewall itself does not control where
logging, it's time to look outside the Shorewall configuration for the Netfilter log messages are written. The LOGFILE setting in
cause. As an example, recent <trademark>SuSE</trademark> releases use <filename>shorewall.conf</filename> simply tells the
syslog-ng by default and write Shorewall messages to <filename>/sbin/shorewall[-lite]</filename> program where to look for
the log. Also, it is important to understand that a log severity of
"debug" will generally be written to fewer log files than a log
severity of "info".</para>
<para>The actual log file where Netfilter messages are written is not
standardized; but anytime you see no logging, it's time to look
outside the Shorewall configuration for the cause. As an example,
recent <trademark>SuSE</trademark> releases use syslog-ng by default
and write Shorewall messages to
<filename>/var/log/firewall</filename>.</para> <filename>/var/log/firewall</filename>.</para>
<para>Please see the <ulink url="shorewall_logging.html">Shorewall
logging documentation</ulink> for further information.</para>
</section> </section>
</section> </section>