On 2/21/11 1:01 PM, davidMbrooke wrote:

> 
> As Tom (Eastep) says, the log files are completely out of Shorewall's
> control.
> 
> For Bering-uClibc 4.x we have 2 separate Shorewall-related logfiles:
>    - /var/log/shorewall-init.log  which is "STARTUP_LOG"
> in /etc/shorewall/shorewall.conf and where the (re-)start messages get
> written.
>    - /var/log/shorewall.log       which is "LOGFILE"
> in /etc/shorewall/shorewall.conf and which is where the kernel writes
> Netfiler messages which contain the string "Shorewall".
> 
> In my experience, shorewall.log only gets created when a message is
> written to that file - so if no packets are REJECTed or DROPped then the
> file is not created (and obviously it is lost when you reboot).
> 

And I should have checked the name of the *STARTUP_LOG* option :-)

Thanks, David
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk 
Collect, index and harness all the fast moving IT data generated by your 
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights. 
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to