From c51f0cb0b4889f063a225b163032c005c0d35f5e Mon Sep 17 00:00:00 2001 From: teastep Date: Mon, 6 Aug 2007 19:48:31 +0000 Subject: [PATCH] Broaden the response to FAQ 16 git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7075 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- docs/FAQ.xml | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/docs/FAQ.xml b/docs/FAQ.xml index c82e1cab4..103420a39 100644 --- a/docs/FAQ.xml +++ b/docs/FAQ.xml @@ -1029,6 +1029,15 @@ DROP net fw udp 10619 Answer: + Just to be clear, it is not Shorewall that is writing all over + your console. Shorewall issues a single log message during each + start, restart, + stop, 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 Shorewall logging + documentation. + Find where klogd is being started (it will be from one of the @@ -1036,7 +1045,7 @@ DROP net fw udp 10619 the appropriate configuration file so that klogd is started with -c <n> where <n> is a log level of 5 or less; - or + and/or @@ -1046,6 +1055,14 @@ DROP net fw udp 10619 + + 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. + + Under RedHat and Mandriva, the max log level that is sent to the