Tobias Kremer wrote: > This is a different problem than the one discussed last week or so! I'm pretty > sure it's a classic race-condition. Then I would suggest placing a lock around the critical region of code. IPC::SRLock perhaps (which I wrote) -- Regards