Bug#269316: [Logcheck-devel] Bug#269316: shorewall rules

[Jari Aalto]

    >     # shorewall stop
    >     # bind restart  
    >     # shorewall start
    > 
    > is pretty usual situation for me. In addition, I do tweak shorewall rules
    > very often, because I have requested new rules to it that are included
    > in next upgrades. I also add or remove services, so shorewall needs
    > restarts at least for following months. I think those start|stop
    > messages cold be ignored by logcheck.

      For you personally they may be good rules, but I have my doubts that
     these are good rules to ship with logcheck itself.

     Perhaps if you could add them to your local rules this would be
     sufficent to stop you from being bothered by these logs, and would
     still allow other users of logcheck to see if their firewalls had
     stopped or started unexpectedly?

I could, but the reason I was suggesting them is that I don't know any way
that shorewall would itself go on or off. It configures iptables and is not
a running process. Those messages are user created and not from any process
that would manipulate it.

Jari