in reply to
Re: Could not catch all children after fork, some of them never end
in thread Could not catch all children after fork, some of them never end
All children are writing to the same BerkeleyDB, but they are using cds_lock/unlock.
I figured out that some loops became endless after pressing CTRL+C, so I added some additional checks. But at one point there could be a problem, so I would try to check manually if a current lock exists, but I could not figure out how this works in BerkeleyDB...does anybody know?