For a couple of weeks now I have noticed that curl doesn't seem to timeout on the master mirror. That is, the connection stays active until I issue <control>-C. In the case below, it sat there for 1 min. and 6 seconds before I exited (at which point it offers me the standard five choices for a not-found url--and works fine).
Is this expected? I know the command line says to allow 30 seconds for a connection, but how long can the connection stay active without any transfer (hint, I've come back to a 15-minute-and-running connection that I had to manually exit). Perhaps it is the server that should be disconnecting and not the client--I don't know. Obviously this isn't a huge problem for me since there's a simple workaround, but I'm curious about whether it is intended. curl --connect-timeout 30 -f -L -A 'fink/0.27.2' -O http://distfiles.master.finkmirrors.net/fontforge_full-20070607.tar.bz2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:01:06 --:--:-- 0^C### execution of curl failed, exit code 2 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
