* zsh 'running wild' after connection loss...
@ 1995-07-17 10:51 Chr. von Stuckrad
0 siblings, 0 replies; only message in thread
From: Chr. von Stuckrad @ 1995-07-17 10:51 UTC (permalink / raw)
To: zsh-workers
Hi!
May be this is an old FAQ-Problem, but I never could find out...
If I work via telnet/rlogin/(tcp/ip)
and have set 'ignoreeof'
and the connection is lost
(and mostly while the 'zsh' is waiting for a running program),
THEN the 'ZSH' loops forever
in 'read(0)' getting nothing from it's 'tty'.
The real problem is the waste of CPU-Time. The 'zsh' uses
100% of the CPU-time (for nothing :-) and the users complain.
Is there a patch for this problem, or does somebody have something
like one of the following (in order of preference :-) :
a) a check for 'closed tty' after 'waiting for a child' ?
b) a timeout (loop only for <adjustable> minutes)
c) a loopcount (give up after <adjustable> times reading nothing)
d) a slowdown (to retry slowly after reading 'nothing) ?
In the moment we use 'zsh-2.5.0c' on Sunos 4.1.3 and Solaris 2.4.
Thanks for bothering with this,
Sincerely your's Stucki
**v** ----v-----------------------------------------------------------
S * | Christoph von Stuckrad | <stucki@math.fu-berlin.de> \
t / * | Dahlem | ...!unido!fub!leibniz!stucki|
u / * | Fachbereich Mathematik, EDV | Tel:+49 30 838-754{9|8} |
<stucki>- - C | Freie Universitaet Berlin | Fax:+49 30 838-5913 |
k \ * | Arnimallee 2-6 | IRC: /nick stucki |
r \ * | D-14195 Berlin | PGP: not yet certified :-( |
a * | Germany | ask for key by mail /
**d** ----^-----------------------------------------------------------
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1995-07-17 10:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1995-07-17 10:51 zsh 'running wild' after connection loss Chr. von Stuckrad
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).