Hi Robert,

Thanks, I have run the script, both on

=> Windows: '2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit
(Intel)]'
=> And on Ubuntu: '2.5.2 (r252:60911, Oct  5 2008, 19:24:49) \n[GCC 4.3.2]'

In both cases the problem appeared almost immediately. I've zipped the
produced log file, the script used, and the console output (files attached),
so you can see for your self.
Also, on linux the logfile is cluttered with a lot of bianry 0 values. This
is consistent with what I saw with my own script.

Regards,

Frans

2009/6/8 Robert Cronk <report@bugs.python.org>

>
> Robert Cronk <cronk.r@gmail.com> added the comment:
>
> P.S. The above script and failure is running on winxp sp3.  Also, if
> you comment out the two os.system() calls, it works just fine.  They
> seem like they should be unrelated to the logging though.  You'll also
> see some errors about access to the blah.txt file which makes sense
> since multiple threads are hitting that file at the same time.  I don't
> know if this is about using os.system() itself from multiple threads
> while logging or if it's about having an error condition during the
> os.system() call on top of that.  Anyway, let me know what you think or
> if I've done something wrong, let me know how to fix it and that might
> be good documentation for others running into this problem.  Thanks.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue4749>
> _______________________________________
>