... so what now? :) If this is an issue in the oracle libraries, is there a version that is known to work on solaris?
--Josh At 9:17 on 11/21/2002 GMT, Tim Bunce <[EMAIL PROTECTED]> wrote: > ----- Forwarded message from Josh Wilmes <[EMAIL PROTECTED]> ----- > > Delivered-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: DBD::Oracle / alarm() problem > From: Josh Wilmes <[EMAIL PROTECTED]> > Reply-To: Josh Wilmes <[EMAIL PROTECTED]> > Date: Wed, 20 Nov 2002 14:40:53 -0800 > > > Tim, > > I appear to be experiencing the problem described at > > http:[EMAIL PROTECTED]/msg13194.html > and > http://groups.google.com/groups?selm=93he36%24egc%241%40nnrp1.deja.com > > This script demonstrates the issue: > > ---- > #!/usr/SD/perl/bin/perl > > #use DBD::Oracle; > use DBI; > > $SIG{ALRM} = sub { print "Caught alarm\n"; }; > > alarm (2); > $dbh = DBI->connect('dbi:Oracle:eman', 'eman', 'eman'); > alarm (0); > > sleep(5); > print "Success\n"; > > ---- > > If the "use DBD::Oracle" line is uncommented, the script succeeds. If > commented out, it fails, and the $SIG{ALRM} handler doesn't work either- > it just prints "Alarm Clock" and exits. > > It appears that the oracle libraries are monkeying with the signal > handlers? > > Here are my versions: > > Solaris 8 > Perl 5.6.1 > DBI 1.30 > DBD::Oracle 1.12 > net8 8.1.7.0.0 > > > I'm not really happy with the "use DBD::Oracle" workaround at this point- > i'd hate to miss some script somewhere while trying to add it. > > If there's a way to fix this in DBD, i'd prefer that, certainly. > > If there's any additional testing I can do to narrow down the issue, please > let me know. > > --Josh > > -- > Josh Wilmes - [EMAIL PROTECTED] > > > > > > ----- End forwarded message ----- >
