On Thu, May 16, 2013 at 11:04 AM, Barry Warsaw <ba...@python.org> wrote:
> On May 16, 2013, at 09:44 AM, Ethan Furman wrote: > > >Is it happening on the same machines? If so, perhaps a daemon to monitor > >those files and then scream and shout when one changes. Might help track > >down what's going on at the time. (Yeah, that does sound like saying > >'inotify' but with more words...) > > No, it's all different kinds of machines, at different times, on different > files. So far, there's no rhyme or reason to the corruptions that I can > tell. We're trying to instrument things to collect more data when these > failures do occur. > Even on machines with ECC ram and reliable storage, not owned by l33t gam0rzs weenies who overclock things? -gps
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
