GKrellM takes a LONG time to start up
I just built a new (ok, not so new, it was spare parts) system. It is a 400MHz PII, with 256MB SDRAM and a 40GIG hard drive. I used alot of parts from my older 300MHz system, and just used the old slackware install that I had on the 40GIG drive because I didn't want to set everything back up. For the most part, everything works fine now, althoguh I have noticed that now GKrellM takes an abnormally long time to start up. It litterally takes about 3 minutes to start. I'm not sure what is causing this. There is no high CPU activitiy durring the time it takes to start, nor is there any abnormally high hard drive activity. On the other system, GKrellM would start up within a second or two... not anything compared to what it's taking now. I think it is trying to connect back to it's self (localhost) and it's not working for one reason or another. I did 'lsof | grep gkrellm' and got (among other things) a thing at the very bottom:
gkrellm 2217 oxagast 6u IPv4 5629 TCP localhost:49910->localhost:7634 (SYN_SENT)
and it just hangs there for a few minutes until GKrellM finally starts, and then if I do 'lsof | grep gkrellm' again, that entery is gone, and some others replaced it after that. This leads me to believe that it's trying to connect back to it's self and it's not working for one reason or another. So I opened a terminal and typed 'ping localhost' and I get no ping responses. It can send, but I don't get a response back. I went and checked my /etc/hosts file, and it all seems to be correct... 127.0.0.1 and 192.168.2.71 point to localhost and fluxy as hostnames for this box. I go to my other computer and ping 192.168.2.71, and from this computer I DO get a response from 192.168.2.71... whats up with that? When I changed network cards, as I am using dhcp, my assigned IP address changed from 192.168.2.86 to 192.168.2.71... could this have something to do with it? If anybody could shed any light onto this, it would be much appriciated.