I said, a signal handler in the _child_ process. If you have opened the database handles in the children (as you should), catching the signal in the parent is much too late; all that's left of the child by then is an entry in the process list. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "ariel mastracchio" <[EMAIL PROTECTED]> To: "Michael A Chase" <[EMAIL PROTECTED]> Sent: Tuesday, February 05, 2002 13:09 Subject: Re: Problems DBI/DBD::Oracle/Perl..
> Have it allready a reaper function in the SIGCHLD > signal handler... > > --- Michael A Chase <[EMAIL PROTECTED]> wrote: > > If the children are being killed by signals, you > > have to trap those signals > > in the child and call exit to allow proper shutdown > > processing to occur. > > Then you can also use an END block if you need to > > handle things more > > gracefully. Normally just allowing the handle > > variables to go out of scope > > (including normal shutdown) is sufficient. > > ----- Original Message ----- > > From: "ariel mastracchio" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, February 05, 2002 12:07 > > Subject: Problems DBI/DBD::Oracle/Perl.. > > > > > I have a server that spawn childs that make > > > connecion to a Oracle DB, the problem is when the > > > childs die, a lot of <defunct> (1 per connection > > lost) > > > left in ps. > > > > > > i put a print "hello" in the SIGCHLD reaper > > > function but this is never called!! > > > > > > All work good if i clean all database use from > > the > > > code.. > > > > > > The SO is Solaris 8, the DB is Oracle 8.1.7... > > > The perl is the 5.6.1 (build with gcc)... > > > The DBI version is 1.20
