apps start slow when not on network

When my Dell Inspiron 8100 Red Hat linux is not connected to the network,
apps take a long time to start. I start emacs from a shell and wait like 3
minutes for it to come up, as oppose to <10 secs when connected. Kdevelop
takes much longer too, but not quite 3 mins. It seems the system first looks
for something over the net (?) Any such experiences or suggestions for a
fix? Thanx.
RM

RM wrote:

> When my Dell Inspiron 8100 Red Hat linux is not connected to the network,
> apps take a long time to start. I start emacs from a shell and wait like 3
> minutes for it to come up, as oppose to <10 secs when connected. Kdevelop
> takes much longer too, but not quite 3 mins. It seems the system first
> looks for something over the net (?) Any such experiences or suggestions
> for a fix? Thanx.
> RM

Found this on Google, try to alias your hostname to localhost (a hostname
resolve issue). Open a terminal, su to root, and issue "hostname -v
localhost", no quotes. You can verify with "hostname -a", should return
localhost. This works to get around extremely slow application launches but
had the following reply when I posted this solution before.

"Oh NOT! Except your computer isn't anyways involved with the internet.
"localhost" is a reserved name, it always should point just to 127.0.0.1
and you will hopefully find that entry in your /etc/hosts under linux,
as well as in /%windir%/system32/drivers/etc/hosts on windoze2K/XP.
You should not change localhost to another IP!"

Since you are just aliasing your computer name to localhost don't see that
the quote applies. Good Luck

On Tue, 26 Aug 2003 09:16:53 -0700, RM <(E-Mail Removed)> wrote:
> When my Dell Inspiron 8100 Red Hat linux is not connected to the network,
> apps take a long time to start. I start emacs from a shell and wait like 3
> minutes for it to come up, as oppose to <10 secs when connected. Kdevelop
> takes much longer too, but not quite 3 mins. It seems the system first looks
> for something over the net (?) Any such experiences or suggestions for a
> fix? Thanx.
> RM

Your computer apparently cannot resolve its own hostname. Since you
do not always have a network connection, assign your hostname to an extra
loopback IP like 127.0.0.2 (it is best not to tamper with localhost line).
That has always worked for me, even when my only network connection was
occassional ppp.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/