Ivan Kurmanov writes
Another stupid idea:
I am not sure about stupid ideas, but am sure about stupid guys who don't check the obvious and that is did you tweak the checks that update daemon
(and/or rid script) does at it's start to ensure that only one copy of the daemon is running at any single moment?
If you somehow get multiple copies of the update deamon running, there might be a chance of them corrupting the database.....
But probably this is bullshit, since berkeley db has a database type for concurrent access and it was the one that I used for update daemon, I think.
I tihnk you are correct, but still it's an avenue worth checking. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel