Messages in this thread | | | From | Bharadwaj Yadavalli <> | Subject | Re: annoying modprobe messages | Date | Thu, 2 Sep 1999 13:54:26 -0400 (EDT) |
| |
Tim Walberg enquired: > Don't know exactly when it started happening, but I think > it was around the time I upgraded to 2.2.1[01]. Recently > I've been getting a series of messages (which unfortunately > don't get logged, and get scrolled off screen pretty quick) > during boot up saying something to the effect that modprobe > can't find lo:1, lo:2, lo:3, ... lo:50 and the same series > of messages for eth0. While I don't think this is hurting > anything, I'm not sure where they're coming from and why, > and that's kind of annoying... > > Any hints?
It looks like there is a bug in /etc/sysconfig/network-scripts/ifup-post. in its present state it is invoking ifup-aliases if $ISALIAS is "no" !! The ifup-aliases script in turn is invoking linuxconf --hint ipalias <device> which actually is generating these error messages.
Just change the following
if [ "$ISALIAS" = yes ] ; then /etc/sysconfig/network-scripts/ifup-aliases ${DEVICE} fi
to
if [ "$ISALIAS" = no ] ; then /etc/sysconfig/network-scripts/ifup-aliases ${DEVICE} fi
and you should be fine shape AFAIK.
Bharadwaj
--
S. Bharadwaj Yadavalli <bharadwaj.yadavalli@compaq.com> AMT, Compaq Computer Corporation <www.digital.com/amt/>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |