From: Mark K. <ma...@pa...> - 2005-08-30 05:21:37
|
This is an odd one : Enlightenment 0.16.7.2 Eterm 0.9.3 on Freebsd 5.4-RELEASE If I start an Eterm that attempts to ssh to an non existent host (e.g) $ Eterm -e ssh user@nosuchhost and then kill the window, I cannot then get another Eterm *or* xterm to start for about 4-6 minutes! The new window is drawn, but immediately vanishes. There is nothing in .xession-errors. Any ideas? Cheers mark |
From: Mark K. <ma...@pa...> - 2005-08-30 05:21:58
|
Mark Kirkwood wrote: > If I start an Eterm that attempts to ssh to an non existent host (e.g) > > $ Eterm -e ssh user@nosuchhost This description is not quite correct. Host must i) exist ii) be down or disconnected, so the Eterm (actually ssh I guess) hangs awaiting a response. |
From: Mark K. <ma...@pa...> - 2005-08-31 10:11:48
|
Mark Kirkwood wrote: > This is an odd one : > > Enlightenment 0.16.7.2 Eterm 0.9.3 on Freebsd 5.4-RELEASE > > If I start an Eterm that attempts to ssh to an non existent host (e.g) > > $ Eterm -e ssh user@nosuchhost > > and then kill the window, I cannot then get another Eterm *or* xterm to > start for about 4-6 minutes! The new window is drawn, but immediately > vanishes. There is nothing in .xession-errors. > More accurate timing is about 60 seconds (the time it takes for ssh to give up connecting). So it looks to me like enlightenment is doing some blocking call awaiting a response from the Eterm window. - Keep those ideas coming :-) Cheers Mark |