This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rcronk
Recipients Frans, lowell87, mramahi77, neyro, rcronk, vinay.sajip
Date 2009-06-09.22:52:47
SpamBayes Score 1.75814e-07
Marked as misclassified No
Message-id <1244587976.2.0.0407929238583.issue4749@psf.upfronthosting.co.za>
In-reply-to
Content
I turned off anti-virus again as well as file indexing and google 
desktop too and still got the errors when I disabled the locks around 
the os.system() calls.

Vinay - when the locks aren't around the os.system() calls, do you get 
the rotating log errors?

I'm still confused at how the os.system calls could be affecting the 
logging at all.  The os.system calls aren't touching the log files.  
Why would it cause them to fail when the os.system calls fail?  It 
seems that when the os.system calls succeed (because of the locks) then 
the logging succeeds but when the os.system calls fail (because the 
locks are disabled), then logging fails.  If, as you suggest, this is a 
race condition that is being exposed by the os.system calls failing 
because they don't have locks around them, then that would be the 
perfect situation (if you can reproduce it) to debug it.
History
Date User Action Args
2009-06-09 22:52:57rcronksetrecipients: + rcronk, vinay.sajip, mramahi77, lowell87, neyro, Frans
2009-06-09 22:52:56rcronksetmessageid: <1244587976.2.0.0407929238583.issue4749@psf.upfronthosting.co.za>
2009-06-09 22:52:48rcronklinkissue4749 messages
2009-06-09 22:52:47rcronkcreate