Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Dan Melomedman <dmelomed at pppl dot gov>
Subject: RE: sybperl scripts never exit
Date: Apr 23 1999 8:28PM

Uhhhh. Upgrade. Also I noticed that if my CGI script does not exit, if it
has a bug, and does not exit, it eats 90 percent of cpu power on the
machine it runs on --NaStY!!!!. 2 or 5 of these scripts on a Spark 5
machine will eat all resources and kill it.

On Fri, 23 Apr 1999, Neil Ratzlaff wrote:

> 1.  The semicolon appears after the print statement in the message I sent out
> to the Sybperl list; I hope this isn't another case where characters get lost
> in transit.  
> 2.  perl -v shows the old version as perl5.002 beta1h.   It doesn't respond to
> the -MSybase switch, though.
> 3.  I don't know what an END{} block is; perl is not something I have
> needed to
> learn yet.
> Neil
> At 15:25 04/23/99 -0400, WORENKLEIN, David, GCM wrote:
> >1. You're missing a semicolon.
> >2. Try perl -v.
> >3. Are there any END{} blocks in your code?
> >
> >
> >-----Original Message-----
> >From: Neil Ratzlaff []
> >Sent: Friday, April 23, 1999 3:05 PM
> >To: SybPerl Discussion List
> >Subject: sybperl scripts never exit
> >
> >
> >Can someone suggest a reason why or way to fix this problem?  Perl scripts
> that
> >use sybase and run under perl5.005/sybperl2.09 never stop - they reach the
> end
> >of the script and apparently never exit, but continue to eat CPU cycles at an
> >alarming rate.
> >
> >These same scripts work properly under an older version of perl, and when I
> run
> >the sybperl version reporting line I get this:  "Unrecognized switch:
> >-MSybase::DBlib(999)".  From a recent post, I suspect the other version is 4,
> >but my boss here thinks it is an early version of perl5.
> >
> >The first line below works (as does everything above it in the script).  The
> >exit line is directly after the print line but seems to not work.
> >
> >print "End of script\n" 
> >
> >exit;
> >
> >Thanks,
> >Neil 
> >