ww, thanks for the response.
I didn't include any code because I don't believe it is the code itself...
(man, how many times have we all heard that?) :)
...however the code would benefit if I could tell if the persisted data is already being written too.
What I have is a honeypot which forks my PERL script to simulate SNMP agents. Occasionally, two set requests might come in at the same time against the same target and try to write to the very same persistent data which I believe is where the corruption happens. I can't really avoid that and feel I need to incorporate these methods to avoid concurrent store requests against the same data.