Re: two copies of my application launched under CGI

I had the same problem with an XP server a few years ago. I feel your pain!

Try running through the server MAPI settings and make sure that your scripts are mapped to the right version of Perl, no duplicates exist, etc. It might be helpful to go through the old server settings and make sure everything maps exactly.

I suspect there may be a different version of Perl on each box, not to mention server patches, etc.

I know you put "use strict;" in your code, so can you post the scripts in question? Someone may spot something that gave them trouble in the past.

Good luck!

-Bilfurd

Comment on Re: two copies of my application launched under CGI

Replies are listed 'Best First'.
Re^2: two copies of my application launched under CGI by rpnoble419 (Pilgrim) on Apr 06, 2009 at 03:03 UTC
I fall on my sword for this. It turns out to be a double call to the application from the HTML code. The HTML file has a textarea that gets data from a scanner via the keyboard buffer. This input is checked via a javascript function called by the onkeyup event. This function is being called twice and the zombie is the result of the second call overriding the first. Thanks to Bilfurd for your reply. And I'm strict on use Strict.	[reply]
Re^3: two copies of my application launched under CGI by almut (Canon) on Apr 06, 2009 at 08:05 UTC
And I'm strict on use Strict. Strictly speaking, it's `use strict` :) — module names are generally case-sensitive (even on Windows). `> perl -e "use strict; $foo=1" Global symbol "$foo" requires explicit package name at -e line 1. Execution of -e aborted due to compilation errors. > > perl -e "use Strict; $foo=1" >` [download] Reason is that - if you `use Strict` - the `use` will implicitly attempt to call `Strict->import`, which isn't found, as the respective namespace is declared with `package strict;` in the module's source (this must 'fail' silently, as a module is not obliged to supply an import method). Thus, any code in an existing `import()` isn't executed, which in turn renders some modules (and in particular pragmata) non-functional, or makes them behave differently... Update: just in case... for whoever downvoted without saying what's wrong (: this of course only applies to Windows, where the respective file is found at all, due to the filesystem being case-insensitive. Geez...	[reply] [d/l] [select]