in reply to DBI, fork, and clone.
I've had this exact same issue for ages now and tried to come up with all sorts of workarounds. I've tried your method in some test code and I'm still seeing that issue you had in previous article regarding all forked connections still use the same handle.
from my test:
sol::kenjim$ ./inactive_test.pl
4326 parent: DBI::db=HASH(0x823d6ec) :1
4327 child: DBI::db=HASH(0x832c4a0) :1
4326 parent: DBI::db=HASH(0x823d6ec) :1
4328 child: DBI::db=HASH(0x832c4a0) :1
4326 parent: DBI::db=HASH(0x823d6ec) :1
4329 child: DBI::db=HASH(0x832c4a0) :1
4326 parent: DBI::db=HASH(0x823d6ec) :1
4330 child: DBI::db=HASH(0x832c4a0) :1
4326 parent: DBI::db=HASH(0x823d6ec) :1
4331 child: DBI::db=HASH(0x832c4a0) :1
the first value is the pid, but each child has the same memory address, so I assume they still are sharing connections. I need each child to have its own connection as well... a little stumped.
In Section
Meditations