Tom Eastep wrote:
Simon Hobson wrote:
Am I right in thinking that this means we can now leave out all those
x y drop policies that are only in there for logging/debugging
purposes ?
Yes.
Nice :-)
I thought so too. This was Paul's idea.
I suppose i had better change my PPS
Using:
shorewall-perl-4.0.1-2
shorewall-4.0.1-2
I have tried everything that I can think of to stop shorewall from puking to
the console. I get dozens if not hundreds of these directed to the console:
Aug 6 07:34:13 backup kernel: Shorewall:net2all:DROP:IN=eth0 OUT=
It's what is defined as console at boot-up that got sent all debug
message...
This one is usually set by the kernel or ulog upon booting - and on the
boot-prompt, you tell the kernel where to send the log-messages. By
default it goes to console.
I'm using it actually quite heavily on my servers -
J and T wrote:
Using:
shorewall-perl-4.0.1-2
shorewall-4.0.1-2
I have tried everything that I can think of to stop shorewall from
puking to the console.
Shorewall is not writing anything to your console. It is klogd that is
writing to your console. Shorewall has no control over where
I didn't mean to offend you Tom by saying Shorewall was puking on my
console. I realize it is klogd. But I've been using Shorewall for years and
now after upgrading only shorewall messages are being sent to the console.
No other system messages are being sent to the console so I was confused as
J and T wrote:
I didn't mean to offend you Tom by saying Shorewall was puking on my
console.
John,
No offense was taken. I just wanted it to be clear, both to you and to
future readers of this thread, that control of logging is outside of Shorewall.
I realize it is klogd. But I've been using
Thanks for the reply Tom. All mine show log level 3 and I have kern.* sent
to /var/log/kernel.log and nothing sent to console, but these are still sent
to console which is strange.
I'm sure I'll figure it out somewhere down the road. It's all about
syslog.conf I know. Something must have
J and T wrote:
Thanks for the reply Tom. All mine show log level 3
Wait a minute -- if you have level 3 configured in Shorewall then you must
set LOGLEVEL=2 in /etc/sysconfig/init in order to suppress the messages
being written to the console.
-Tom
--
Tom Eastep\ Nothing is foolproof to a
My firewall is using shorewall 3.0.x and CentOS
Recently, I found that firewall is attaching from ARP spoofing..
There are a lot of out of socket memory in messages log
-
This SF.net email is sponsored by: Splunk Inc.
Still
Of course!
--
Tip
Under RedHat and Mandriva, the max log level that is sent to the console is
specified in /etc/sysconfig/init in the LOGLEVEL variable. Set
#8220;LOGLEVEL=5#8221; to suppress info (log level 6) messages on the
console.
--
It makes perfect sense now that I put two and
10 matches
Mail list logo
