lynx-dev connect_timeout doesn't catch idle connections

[Danielle Ghanine]

brief:
the "-connect_timeout" option doesn't babysit connections
which are established but for some other reason become idle.


detail:

the command being executed, wrapped for mail and with
the username/password info removed, was:

echo '(form data)' | eval $lynx -accept_all_cookies \
-cookie_file=~/Mail/.cookies.txt -connect_timeout=600 \
-post_data -dump \
http://localhost/webmail/src/redirect.php > /dev/null

i expected this to run for no longer than 10 minutes
but, in running it every 30 seconds for a day, i've
seen the following behavior more than once.  

lynx said:
(begin quote)
Looking up localhost
localhost
Making HTTP connection to localhost
Sending HTTP request.
HTTP request sent; waiting for response.
HTTP/1.1 302 Found
Data transfer complete
HTTP/1.1 302 Found
Location URL is not absolute.
Looking up localhost
localhost
Making HTTP connection to localhost
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Socket read failed for 180,000 tries.
Connection interrupted.

lynx: Can't access startfile http://localhost/webmail/src/redirect.php
(end quote)

the bash script running lynx said it took 18018
seconds to execute.  this is 300 minutes or 5 hours,
definately longer than the ten minutes given on the
command line.

404-duncan:~/bin$lynx -version
Lynx Version 2.8.4rel.1 (17 Jul 2001)
libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 0.9.6b
Built on linux-gnu Jan 22 2003 13:17:01


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden