On Thu, 2014-10-16 at 20:45 -0700, Bill Landry wrote: > Also, I don't feel that ignoring failed database downloads is prudent. > Most admins what to know right away if there is a problem with a > download site. When I get some time I'll take a look at the provided > patch to see if any of the suggested changes make sense.
The main problem with the current code is that the amount of cron spam is high due to temporary connection issues. I think that the code should track when the last successful download and install was and only send an error to the cron job output recipient if a particular file is more than 24 hours out of date. The report could include the last 3 or 4 errors. Obviously all errors should be logged though for debugging when the admin discovers the problem. Any thoughts Bill? I would love to be able to get this fixed in the next Debian release. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
