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

Broaden the response to FAQ 16

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7075 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-08-06 19:48:31 +00:00
parent 0d384f7575
commit c51f0cb0b4
1 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/FAQ.xml
View File

@ -1029,6 +1029,15 @@ DROP net fw udp 10619</programlisting>
<para><emphasis role="bold">Answer:</emphasis></para> <para><emphasis role="bold">Answer:</emphasis></para>
<para>Just to be clear, it is not Shorewall that is writing all over
your console. Shorewall issues a single log message during each
<command>start</command>, <command>restart</command>,
<command>stop</command>, etc. It is rather the klogd daemon that is
writing messages to your console. Shorewall itself has no control over
where a particular class of messages are written. See the <ulink
url="shorewall_logging.html">Shorewall logging
documentation</ulink>.</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Find where klogd is being started (it will be from one of the <para>Find where klogd is being started (it will be from one of the
@ -1036,7 +1045,7 @@ DROP net fw udp 10619</programlisting>
the appropriate configuration file so that klogd is started with the appropriate configuration file so that klogd is started with
<quote>-c <emphasis>&lt;n&gt;</emphasis> </quote> where <quote>-c <emphasis>&lt;n&gt;</emphasis> </quote> where
<emphasis>&lt;n&gt;</emphasis> is a log level of 5 or less; <emphasis>&lt;n&gt;</emphasis> is a log level of 5 or less;
or</para> and/or</para>
</listitem> </listitem>
<listitem> <listitem>
@ -1046,6 +1055,14 @@ DROP net fw udp 10619</programlisting>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<warning>
<para>The hints below are just that; they have been known to work with
at least one release in the past but are not guaranteed to continue to
work with all releases of a particular distribution. As described
above, you may have to hunt around in your distribution's init scripts
in order to find the correct solution.</para>
</warning>
<tip> <tip>
<para>Under RedHat and Mandriva, the max <ulink <para>Under RedHat and Mandriva, the max <ulink
url="shorewall_logging.html">log level</ulink> that is sent to the url="shorewall_logging.html">log level</ulink> that is sent to the