http://www.perlmonks.org?node_id=1023319


in reply to Could not catch all children after fork, some of them never end

Wild guess: Are the children writing to the same db? (B)locking issues?

Replies are listed 'Best First'.
Re^2: Could not catch all children after fork, some of them never end
by krabbl (Initiate) on Mar 14, 2013 at 16:08 UTC

    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?