On 6/15/17 11:36 AM, [email protected] wrote:
> Note, however, that it does eventually connect. As far as I can tell,
> it
> does always eventually connect.
>
> Needless to say, when I first hit this problem, I assumed it had hung,
> and
> when I tried to kill it, I ran into the problems described above.
It's all system calls. If it hangs in `connect', bash has to wait until
the system call returns one way or another. There is no provision for a
timeout with connect, and any signal (e.g., SIGALRM) that bash tries to
set for a timeout will be deferred until connect completes or fails
anyway.
>
> Also note: In testing this, I found that if I do hit ^C while it is
> hung,
> then wait long enough, eventually it does exit as shown below:
>
> Elapsed time for this 'exec' ... ^C^C^C^Cbash: connect: Connection
> refused
> bash: /dev/tcp/localhost/12345: Connection refused
If that's a legit error, the problem might be with the server.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
