From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2)
Description of problem:
When there are .OLD backup files which contain the same information then the
script will error on the first such alias.
This causes any later aliases to not be loaded.
Version-Release number of selected component (if applicable):
# rpm -q initscripts
Steps to Reproduce:
1. have more than one alias, e.g. ifcfg-eth0:0 and ifcfg-eth0:1
2. copy ifcfg-eth0:0 to ifcfg-eth0:0.OLD
3. run ./ifup-aliases eth0
Actual Results: observe the error and notice that ifcfg-eth0:1 never was run.
./ifup-aliases: line 3: devseen_0.OLD=ifcfg-eth0:0.OLD: command not found
error in ifcfg-eth0:0.OLD: already seen ipaddr 126.96.36.199 in ifcfg-eth0:0
Expected Results: possibly that configuration should be skipped without
stopping the whole process.
possibly a more complex backup exclusion is needed.
I knew that my second alias was properly configured, could not figure out why it
wouldn't load after reboot.
I don't believe .OLD is a normal editor backup file... that's why it's read.
Two reasons why I believe this needs to be fixed:
1- the network configuration should be loaded even if there are errors in one of
the files, the subsequent files should be read.
2- This is not caused by a normal editor. It is caused by RedHat's upgrade process.
Note a few other ocurrances of this problem:
Redhat's network configuration utilities should not create these files, but if
they do, ifup-aliases should continue working.
This bug was not about the creation of the files or even the exitance of such
files, but that fact that ifup-aliases would cease working upon the first error
I believe that it should report the error and continue to load the other valid
Looking at current redhat-config-network code, I don't see it creating .OLD; but
you're right, it shouldn't bail completely.
initscripts-8.26-1 were fixed to ignore incorrectly named files, and to continue
on errors in alias files.
Thanks for your report.