> > Actually, I tried exactly this, and then sent a "normal heavy" load through > > my SpamAssassin script to test it, and there were times when the temp file > > would be overwritten before the current spamc process was done with it. I > > found you have to keep the data flowing (such as sequential pipes) otherwise > > you have to start locking files. > > Use "mktemp" (or "tmpfile", depending upon your context) to create a > temporary file with a unique name, then there's no danger of overwriting.
Excellent idea! Did that and it works well. Just need to go over it and optimize it a bit now. Thanks!
