extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-07 14:08:52 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update release documents for Debian insserv change

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-06-25 11:16:06 -07:00
parent 463e22bdb6
commit 508cf25a70
3 changed files with 21 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Shorewall/changelog.txt
View File

@ -1,12 +1,13 @@
Changes in Shorewall 4.4.10.1
Changes in Shorewall 4.4.10.2
1) Fix start priority of shorewall-init on Debian
1) Make IPv6 log and connections output readable.
2) Make IPv6 log and connections output readable.
2) Add REQUIRE_INTERFACE to shorewall*.conf
3) Add REQUIRE_INTERFACE to shorewall*.conf
3) Avoid run-time diagnostic when options are omitted from
shorewall*.conf.
4) Avoid run-time diagnostic when options are omitted from shorewall*.conf.
4) On Debian, run insserv when it is installed.
Changes in Shorewall 4.4.10.1

20
Shorewall/known_problems.txt
View File

@ -20,19 +20,12 @@
executed the above command to work around the problem, we recommend
that you remove /etc/shorewall/capabilities.
3) On Debian and derivatives, shorewall-init is starting too late.
To work around this issue, at a root prompt:
cd /etc/rcS.d
mv S38shorewall-init S08shorewall-init
4) The new REQUIRE_INTERFACE option was not added to shorewall.conf
3) The new REQUIRE_INTERFACE option was not added to shorewall.conf
and shorewall6.conf.
You can simply add it if you need it.
5) Under Perl 5.12.1, a harmless Perl run-time diagnostic is
4) Under Perl 5.12.1, a harmless Perl run-time diagnostic is
produced when options are omitted from shorewall.conf or
shorewall6.conf.
@ -41,3 +34,12 @@
Use of uninitialized value
$Shorewall::Config::config{"REQUIRE_INTERFACE"} in lc at
/usr/share/shorewall/Shorewall/Config.pm line 1902.
5) On Debian and Debian-based systems, the start/stop priorities of
Shorewall products may be incorrect when the insserv package is
installed.
You may correct this problem by running insserv (as root).

6
Shorewall/releasenotes.txt
View File

@ -220,8 +220,10 @@ I I I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
4.4.10.2
1) The start priority of shorewall-init on Debian and Debian-based
distributions was previously too low, making it start too late.
1) The start priorities of the Shorewall products were incorrect on
Debian when the insserv package is installed. This is corrected for
new installs, but existing users who have both insserv and a
Shorewall product are urged to run insserv just be be sure.
2) The log output from IPv6 logs was almost unreadable due to display
of IPv6 addresses in uncompressed format. A similar problem