The sourceforge mail server was down so I am resending:
Problem solved Tom. I'm sure I'll look like an idiot here Tom because you provided the answer in your FAQ 16 all along. Now you can say "I told you so" and I'm sorry for not understanding your FAQ. (FAQ 16) Shorewall is writing log messages all over my console making it unusable! -- 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 “LOGLEVEL=5” to suppress info (log level 6) messages on the console. -- But this only has an effect at boot up. It is then overwritten by syslog. I can set this to anything at all and Shorewall messages will still be sent to the screen after boot. The answer is with your SUSE Tip: vi /etc/sysconfig/syslog KLOGD_OPTIONS="-x" to: KLOGD_OPTIONS="-x -c (n)" Where "(n)" is a number from 0-7: 7 - debug (Debug-level messages) 6 - info (Informational) 5 - notice (Normal but significant Condition) 4 - warning (Warning Condition) 3 - err (Error Condition) 2 - crit (Critical Conditions) 1 - alert (must be handled immediately) 0 - emerg (System is unusable) After adding the -c (n), Shorewall's kernel messages are now sent to the "/var/log/kernel.log" as I have defined in my "/etc/syslog.conf" file instead of the console. I think the most confusing part about all this is how many different configuration files make up the logging. The biggest problem is in the naming of their files: /etc/syslog.conf <- you would think it would be done here. After all, this is the "conf" file. /etc/sysconfig/syslog <- while it doesn't state "conf", it is indeed the configuration file you need to be working on. This exists at least as far back as Red Hat 7.3. So you had the answer in your FAQ page, but I didn't bother to look at the non Red Hat tips since I use Fedora 7 and CentOS (all Red Hat). Sorry for not understanding all this. Logging is something I don't deal with on a day-to-day basis. I think the last time I modified any of this was back in 2002. Have a great day, John >J and T wrote: > > No other messages are dumped there, just Shorewall. If > > I log in from another box using SSH, no shorewall messages are seen. But >as > > soon as I go back to the server room, Shorewall messages are scattered >on > > the server's console (login prompt). > > > > It's weired don't you think? > >Not especially, given that you are using such a high priority (level) for >Netfilter messages. I imagine that those are the only messages being logged >with priority 0-3. > >-Tom >-- >Tom Eastep \ Nothing is foolproof to a sufficiently talented fool >Shoreline, \ http://shorewall.net >Washington USA \ [EMAIL PROTECTED] >PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key > ><< signature.asc >> >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Shorewall-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/shorewall-users _________________________________________________________________ Puzzles, trivia teasers, word scrambles and more. Play for your chance to win! http://club.live.com/home.aspx?icid=CLUB_hotmailtextlink ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
