RE: What happens to a db-library handle on a fork?
"Wechsler, Steven" <[email protected]>
| Newsgroups | gmane.comp.lang.perl.modules.dbi.sybase |
|---|---|
| Message-ID | <E67053DABCCDF4428BB7974550E1108F01089083@DIRECTEFFECT.mtvn.ad.viacom.com> |
That's what I suspected. Thanks. Steve -----Original Message----- From: Michael Peppler [mailto:[email protected]] Sent: Thursday, February 03, 2005 12:34 PM To: '[email protected]' Subject: Re: What happens to a db-library handle on a fork? On Thu, 2005-02-03 at 17:35, Wechsler, Steven wrote: > I'm creating a loop which will create multiple chld processes. Before > the loop I open up a DB handle, which needs to stay open while this > fork occurs, but the children do not need access to the database. > Should I explicitly close the handle in each child, just ignore it, or > do something else? You should probably ignore it. If you close it explicitly I suspect that the server will see that as the connection being closed, and the parent will get an error if it tries to access it. Michael -- Michael Peppler - [email protected] - http://www.peppler.org/ Sybase DBA/Developer Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html