thanks for preceeding answer. I have two others :
1/ is it going to be fixed in a future release of DBI ?
I am sure Tim will fix it.
2/ if I don't want to trace DBI can I ignore the trace file in children
processes created by modperl ?
Yes you can ignore it
Gerald
The following change fixes that, but now the trace filehandle is not
cloned
anymore. That means you have to set the trace file in every thread and
cannot set it in the parent thread.
DBI.xs line 223
change from
DBIS-logfp = parent_dbis? fp_dup(parent_dbis-logfp,'',0) :