If this were not working ( and it is), the ifup-eth0:0 would not work at all
and I would not get the delay message.
The problem is not that the script is being recognized. It is that the ifup
file checks the interface via the ifconfig eth0:0. Since this function
indicates that the device is unavailable, it cancels the running of the
script.
Michael Johnson at RedHat seems to think that he has a change in the
Initscript that will correct this.
Thanks for the help though.
----------
From: jst@uwasa.fi
To: ATPLACK@scj.com
Subject: Re: IP_Alias and SysVInit
Date: Monday, September 30, 1996 6:23PM
> Okay I am trying to setup an alias for my eth0 interface. I am using
> SysVInit on a Rembrandt Installation (Same thing on Slackware install so
> it is not this version).
>
> I have the rc3.d/S10network file runing the ifup in the
> /etc/sysconfig/network-scripts directory.
>
> Inside this directory I have the ifcfg-eth0 file and I also have create
> a ifcfg-eth0:0 file with the correct settings.
>
seems OK
> This all seems to "run" correctly. from the init script except that the
> alias is being "Delayed".
>
> I traced the problem to the following line:
> /sbin/ifconfig ${DEVICE} 2>&1 | grep -s "unknown interface" > /dev/null
>
> if I run this line, step by step, I find out that the "/sbin/ifconfig
> eth0:0 2>&1" or "/sbin/ifconfig eth0:0" comes back with the following
> error:
> eth0:0::unknown interface
>
> The following line DOES work:
> /sbin/ifconfig eth0:0 192.168.1.1
>
> I am running ifconfig version 1.20 (Rembrandt) or ifconfig version 1.22
> (Slackware)
>
> Questions
> 1. Is this the correct place to put IP aliases for boot time loading?
You have as far as I know done absolutly the correct thing in creating
the file /etc/sysconfig/network-scripts/ifcfg-eth0:0, the problem is
that the /etc/rc.d/init.d/network that comes with RedHat doesn't check
for these files, below is a untested patch that should fix it ("cd
/etc/rc.d/init.d; patch file_where_patch_is")
This is from RedHat 3.0.3 so it might have changed but you get the
point...
--- network.orig Tue Oct 1 01:29:05 1996
+++ network Tue Oct 1 01:29:56 1996
@@ -30,7 +30,7 @@
if [ "${PCMCIA}" = "yes" ]; then
echo "Delaying eth initialization for pcmcia card manager"
else
- for i in ifcfg-eth?; do
+ for i in ifcfg-eth? ifcfg-eth?:? ; do
if [ -e $i ]; then
./ifup-eth $i boot
fi
> 2. Why does ifconfig not see that alias interface like this? Is there a
> patch for this?
ifconfig does se it but the network script doesn't
> 3. Is the problem in the init scripts or in ifconfig?
init scripts...
> 4. What does "2>&1" do? I cannot find it anywhere.
it redirects the stderr of the process to stdout (this is a bash
feature, "man bash" might tell you)
>
> TIA
Hope this helps...
--
Johnny Stenback, programmer / University of Vaasa, Computer Centre
E-Mail jst@uwasa.fi, Phone +358 61 3248 387, +358 50 5575 094