I read through the doc''s and I didn''t find anything about stopping Shorewall while upgrading so I left it running. All is still well I''m just wondering why these two files were created? After installing the 1.4.4b rpm I get the following. [root@localhost Documents]# rpm -Uvh --nodeps shorewall-1.4.4b-1.noarch.rpm Preparing... ########################################### [100%] 1:shorewall warning: /etc/shorewall/rules created as /etc/shorewall/rules.rpmnew warning: /etc/shorewall/zones created as /etc/shorewall/zones.rpmnew ########################################### [100%] [root@localhost Documents]# cd /etc/shorewall [root@localhost shorewall]# dir blacklist interfaces params rules stopped zones.rpmnew common.def maclist policy rules.rpmnew tcrules ecn masq proxyarp shorewall.conf tos hosts modules rfc1918 start tunnels init nat routestopped stop zones [root@localhost shorewall]# shorewall version 1.4.4b Is it better to stop shorewall first before upgrading and/or applying a patch that comes out? No worries, I just didn''t see this mentioned at all. Thanks, JBanks __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
> /etc/shorewall/rules created as > /etc/shorewall/rules.rpmnew > warning: /etc/shorewall/zones created as > /etc/shorewall/zones.rpmnew> Is it better to stop shorewall first before upgrading > and/or applying a patch that comes out? > No worries, I just didn''t see this mentioned at all.Doesnt make a difference if you stop it or not. This means that the two files were not identical to the one in the new rpm, and they are tagged as config files, and hence they are not replaced. You should: 1. Stop shorewall 2. Make backup copies of your current rules & zone file 3. copy the *.rpmnew files to rules & zones 4. Migrate the old settings into the new files 5. Restart shorewall (Yes, you can do this in tons of different ways, but that is the order i like to do things in)
Forgot to mention that I was running 1.4.3 before upgrading to 1.4.4b. I also issued a Shorewall "save" command before upgrading. JBanks --- Joshua Banks <l0f33t@yahoo.com> wrote:> I read through the doc''s and I didn''t find anything > about stopping Shorewall while upgrading so I left > it > running. > All is still well I''m just wondering why these two > files were created? > > After installing the 1.4.4b rpm I get the following. > > [root@localhost Documents]# rpm -Uvh --nodeps > shorewall-1.4.4b-1.noarch.rpm > Preparing... > ########################################### [100%] > 1:shorewall warning: > /etc/shorewall/rules created as > /etc/shorewall/rules.rpmnew > warning: /etc/shorewall/zones created as > /etc/shorewall/zones.rpmnew > ########################################### [100%] > [root@localhost Documents]# cd /etc/shorewall > [root@localhost shorewall]# dir > blacklist interfaces params rules > > stopped zones.rpmnew > common.def maclist policy rules.rpmnew > > tcrules > ecn masq proxyarp shorewall.conf > > tos > hosts modules rfc1918 start > > tunnels > init nat routestopped stop > > zones > [root@localhost shorewall]# shorewall version > 1.4.4b > > > Is it better to stop shorewall first before > upgrading > and/or applying a patch that comes out? > No worries, I just didn''t see this mentioned at all. > > Thanks, > JBanks > > > > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > _______________________________________________ > Shorewall-users mailing list > Post: Shorewall-users@lists.shorewall.net > Subscribe/Unsubscribe: >http://lists.shorewall.net/mailman/listinfo/shorewall-users> Support: http://www.shorewall.net/support.htm > FAQ: http://www.shorewall.net/FAQ.htm__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
Thanks j2, So when your saying that the reason the *.rpmnew files were made because the new files were different from the older ones, what is different? The coding or just the extra text added inside the new files? The extra text is apparent when I "diff" the two files. Is this a behaviour of RPM when it notices differences to automatically create new files? Just curious. Thanks, JBanks --- j2 <spamfilter2@mupp.net> wrote:> > /etc/shorewall/rules created as > > /etc/shorewall/rules.rpmnew > > warning: /etc/shorewall/zones created as > > /etc/shorewall/zones.rpmnew > > > Is it better to stop shorewall first before > upgrading > > and/or applying a patch that comes out? > > No worries, I just didn''t see this mentioned at > all. > > Doesnt make a difference if you stop it or not. This > means that the two > files were not identical to the one in the new rpm, > and they are tagged as > config files, and hence they are not replaced. You > should: > > 1. Stop shorewall > 2. Make backup copies of your current rules & zone > file > 3. copy the *.rpmnew files to rules & zones > 4. Migrate the old settings into the new files > 5. Restart shorewall > > (Yes, you can do this in tons of different ways, but > that is the order i > like to do things in) >__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
> So when your saying that the reason the *.rpmnew files > were made because the new files were different from > the older ones, what is different?Compare them and see for yourself.> Is this a behaviour of RPM when it notices differences > to automatically create new files?Really up to whomever creates the RPM, but the default is to never overwrite any config files.
Thanks for the response j2. I followed your instructions and did a "diff" on the files and there are some minor text changes within the two new files in comparison to the older ones.I talked about earlier. Made backups of the originals and then moved the new ones onto the old ones and then modified the new ones with my old config settings. All is well. Thanks. JBanks --- j2 <spamfilter2@mupp.net> wrote:> > So when your saying that the reason the *.rpmnew > files > > were made because the new files were different > from > > the older ones, what is different? > > Compare them and see for yourself. > > > Is this a behaviour of RPM when it notices > differences > > to automatically create new files? > > Really up to whomever creates the RPM, but the > default is to never overwrite > any config files. >__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com