LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   ifdown eth0 slows the typing down (???) (https://www.linuxquestions.org/questions/linux-general-1/ifdown-eth0-slows-the-typing-down-113338/)

fcarli 11-07-2003 02:56 AM

ifdown eth0 slows the typing down (???)
 
Expert,

I have a problem and I have no idea where it can come from.
I have 2 network interfaces (eth0 and wlan0).
I don't think wlan0 has anything to do with it but still, it may be worth mentionning.

the problem is simple.
When I have not done a "ifup eth0",since the last reboot, no pb.
When I decide to use eth0 and therefore do a "ifup eth0" no pb.
When I decide I don't need eth0 anymore and do a "ifdown eth0", then all the typing in linux is slowing down : in the console, in an xterm, in mozilla ... everywhere.

top does not show any special cpu activity.

if I ifup eth0 gain, typing goes normal again
if I ifdown eth0 again, typing goes slow again ...

Putting wlan0 up or down before or after eth0 makes absoluely no difference.

any idea ?

Thank you

SlickWilly 11-07-2003 10:45 AM

I'm going to have a stab at this. Be warned it's a stab in the dark...

Some window managers (Gnome is what I'm thinkin' here) have issues when they can't resolve their local hostname. It's possible that your ifdown eth0 is removing a hostname entry from your hosts, or a resolv.conf entry to resolve your machine's name. The issues are basically 'slowness'. Windows draw slowly, clicks respond slowly, and although I'm not entirely sure if the 'keyboard responds slowly', it might also be in that list of things which 'don't work right'.

Solution to the problem is to include your hostname in the 127.0.0.1 line in your hosts file.

LIke :

127.0.0.1 puck.fairies.net localhost.localdomain localhost

That way when your window manager tries to resolv its own name (X windows is a network'd display type and it *needs* some kind of networking resolution ability to run correctly) it gets something back. If it doesn't, it can continue to work.. sortof, but wierd things happen, including the slowness mentioned above.

Give this a whirl, if it's not that then my only other thought is an interupt problem where you've got your nic0 tied to the keyboard interupt... However that is *exceptionally* unlikely and would only have come about by a *really* foobar'd installation.

Slick.


All times are GMT -5. The time now is 02:06 AM.