On Thu, 13 Aug 2009 10:50:49 -0600 Nicholas Leippe <[email protected]> wrote:
> 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. Thanks, all good suggestions. A bit of research indicated that the problem occurs when I go through my local apt-cache machine. It does not occur when I bypass it and go directly to the mirror server. So.... I need to either dig into apt-cacher, or else add a work-around to the cron script. Or something. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
