On Tue Aug 11 2009 12:37:30 Charles Curley wrote: > > The same failures occur when I run the command "apt-file update" > manually. I then run wget or curl using the URL given in the error > message, and the file comes in just fine. This suggests a timeout > problem with apt-file. Is there an elegant way to determine what that > timeout is? And then to change it? That is, something short of hacking > the apt-file script itself?
Perhaps you can change the timeout via the .curlrc file. You may have to temporarily hack the script to discover the current timeout, or, you could rename curl and replace it w/a wrapper to get/change the settings. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
