MozillaFirebird taking unusually long time to open

[lizardloop]

For some months now I have been using MozillaFirebird with no prelinking and fluxbox. I've found it opened in a very acceptable time up until about a day a go. Now it takes about 10 seconds longer to open MozillaFirebird. during the extra 10 seconds absolutely no hard drive access occurs. Its as though it just decides to take a break for awhile. I'd rather not have to start prelinking things as I've never needed to before.
My current version of MozillaFirebird is 0.6.1. I performed an "emerge -u world --deep" about 2 weeks ago.

[GentooBox]

you could try the new 0.7 - its really nice.
i've seen some other post around where where ppl have some performance issues.

try searching

[QPegasus]

Have you recompiled your kernel lately? Or changed anything with hdparm?

I had a similar startup time with Firebird (during the first run), and the problem was that I forgot to select the support for my IDE driver when making my kernel.

[lizardloop]

Funnily enough I didn't have the IDE drivers for my Epia 800 compiled for some months and only installed them recently.
I'll try the new version of firebird and if that doesn't solve it then I'll uncompile my IDE drivers.

[lizardloop]

Well I've installed .7 but it hasn't improved. if anything it worse. When I open it the hard drive doesnt do anything for about 5 seconds, then does a couple of short bursts, then nothing again for about 5 seconds, then it loads. It's really starting to irritate me as it reminds of what windows does when it startups.

[Apolonius]

Whats the output of:
cd /usr/lib/MozillaFirebird/;./run-mozilla.sh ./MozillaFirebird-bin

Do you have any relocation error ? (flash plugin for instance)

[eee]

A co-worker of mine was having similar problems. Turned out that he had his DNS mis-configured (bind wasn't started, but nsswitch.conf specified to try there first, I think). If nothing else works, consider reviewing /etc/nsswitch.conf, /etc/resolv.conf, /etc/hosts are set up correctly and ensuring that hostname and domainname are all set properly on boot.

Kind of a long shot, but ya never know.

[lizardloop]

A co-worker of mine was having similar problems. Turned out that he had his DNS mis-configured (bind wasn't started, but nsswitch.conf specified to try there first, I think). If nothing else works, consider reviewing /etc/nsswitch.conf, /etc/resolv.conf, /etc/hosts are set up correctly and ensuring that hostname and domainname are all set properly on boot.

Kind of a long shot, but ya never know.

Turned out a day or so ago I changed my hostname. Turns out I didn't update /etc/hosts. Thank you very much for the tip, solved the problem completely.