forked from extern/shorewall_code
Fix shorewall.spec so that Shorewall will start up at boot
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1606 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
b86d3f03d9
commit
5cf57190fb
@ -64,3 +64,6 @@ Changes since 2.0.3
|
|||||||
30) Verify Physdev match if BRIDGING=Yes
|
30) Verify Physdev match if BRIDGING=Yes
|
||||||
|
|
||||||
31) Don't NAT tunnel traffic.
|
31) Don't NAT tunnel traffic.
|
||||||
|
|
||||||
|
32) Fix shorewall.spec to run chkconfig/insserv after initial install.
|
||||||
|
|
||||||
|
@ -47,6 +47,10 @@ Problems corrected since 2.1.7
|
|||||||
allows tunnel mode IPSEC to work for local networks where some of
|
allows tunnel mode IPSEC to work for local networks where some of
|
||||||
the systems use one-to-one NAT.
|
the systems use one-to-one NAT.
|
||||||
|
|
||||||
|
4) The shorewall.spec file now directs rpm to cause Shorewall to start
|
||||||
|
automatically at boot. This feature was inadvertently removed in
|
||||||
|
Shorewall 2.1.3.
|
||||||
|
|
||||||
-----------------------------------------------------------------------
|
-----------------------------------------------------------------------
|
||||||
Issues when migrating from Shorewall 2.0 to Shorewall 2.1:
|
Issues when migrating from Shorewall 2.0 to Shorewall 2.1:
|
||||||
|
|
||||||
|
@ -40,6 +40,14 @@ rm -rf $RPM_BUILD_ROOT
|
|||||||
|
|
||||||
%post
|
%post
|
||||||
|
|
||||||
|
if [ $1 -eq 1 ]; then
|
||||||
|
if [ -x /sbin/insserv ]; then
|
||||||
|
/sbin/insserv /etc/rc.d/shorewall
|
||||||
|
elif [ -x /sbin/chkconfig ]; then
|
||||||
|
/sbin/chkconfig --add shorewall;
|
||||||
|
fi
|
||||||
|
fi
|
||||||
|
|
||||||
%preun
|
%preun
|
||||||
|
|
||||||
if [ $1 = 0 ]; then
|
if [ $1 = 0 ]; then
|
||||||
|
Loading…
Reference in New Issue
Block a user