Being lazy, I have a weeky cron job to run apt-file update. It appears to not get the diffs, like so:
curl: (22) The requested URL returned error: 404 Download of http://mirrors.xmission.com/ubuntu/dists/jaunty/Contents-i386.diff/Index failed It then apparently goes for the full index, and that also fails: curl: (18) transfer closed with 435742 bytes remaining to read Download of http://mirrors.xmission.com/ubuntu/dists/jaunty/Contents-i386.gz failed Command exited with code 18 According to the curl man page, the errors are: 18 Partial file. Only a part of the file was transferred. 22 HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f/--fail is used. 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? Thanks -- 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. */
