On 12/12, John Hardin wrote: > Yeah, that would explain the masscheck behavior. Anybody want to > fire off a test and see if this fixed the long runtimes?
Nice, thanks. It seems like we should make some attempt at monitoring for drastic changes in masscheck run time. Like, I don't know, keep a log of how long it takes each day, and maybe email an error to the person running it if it runs a lot longer than usual. -- "The whole aim of practical politics is to keep the populace alarmed -- and hence clamorous to be led to safety -- by menacing it with an endless series of hobgoblins, all of them imaginary." - H. L. Mencken http://www.ChaosReigns.com
