In article <3u2les$gqh@engnews2.Eng.Sun.COM> Casper.Dik@Holland.Sun.COM (Casper H.S. Dik - Network Security Engineer) writes:
jhall@datamap.mn.org writes:
[..]
>know I'm safe there. But this time when I boot, I get the error:
>"ifconfig: bad address le0". What's going on!?
This means that ifconfig thinks that "le0" is the hostname to set for
the interface.
Okay, I'm a dummy. Here's what's happening:
There is nothing wrong with ifconfig. It's a silly admin mistake, and
one that shouldn't have happened. We don't have NIS yet (working
towards that!) so last week when I updated all the /etc/hosts files on
our UNIX network, I had to do so manually.
Simply, the copy of "hosts" that I updated across the network didn't
have this machine listed. One of the things ifconfig does at boot
time is check /etc/hosts for its IP address. Didn't have one,
therefore "ifconfig: bad address".
-- new improved .sig: -- James Hall, systems administrator || phone: 612-934-0900 email: jhall@datamap.mn.org || fax: 612-934-8727 Vista Information Solutions || 7525 Mitchell Road (formerly DataMap) || Eden Prairie, MN 55344 -- James Hall, systems administrator || phone: 612-934-0900 email: jhall@datamap.mn.org || fax: 612-934-8727 Vista Information Solutions || 7525 Mitchell Road (formerly DataMap) || Eden Prairie, MN 55344
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:29 CDT