* Paul Gear <[EMAIL PROTECTED]>: > That is true, but in both of the machines i've upgraded to Shorewall > 3.2.4, they have not started successfully. Shorewall does not start > without the STARTUP_ENABLED variable being present, which i think is bad > backwards-compatibility behaviour. I'll have a talk to Tom about this.
I'm sorry for the mess. I closed the bug while it was still open. I uploaded a new version of the package which sets by default STARTUP_ENABLED=YES, such that upgrade on a machine without an up-to-date shorewall.conf shouldn't give problems any more. -- lorenzo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
