Hi Jere,
I noticed this happening a couple times since you fixed one aspect of this issue. Before DirMon would crash when it tried to delete a file but couldn't for some reason (usually it was still in use). Now it doesn't crash, but goes in an endless loop trying to delete the file. It keeps on trying endlessly, taking up 100% cpu and basically will stop processing files since it's too busy trying to delete the file. Here's a sample of the log:
2006-Aug-13 23:41:23 - Attempting to delete: D:\Recordings\EntertainmentTonight-1629675-0.log
2006-Aug-13 23:41:23 - boost::filesystem::remove: "D:\Recordings\EntertainmentTonight-1629675-0.log": The process cannot access the file because it is being used by another process.
When this happens, the log file grows insanely huge with a gazillion of those statements... I have one that is a gig and a half
Edit: It looks like SA was stuck on the "EntertainmentTonight" job and that's why DirMon couldn't delete it. Sage already deleted the mpg... I have some sort of Undelete running on my server so I'll see if I can restore the mpg and run SA on it to see why it hung up.