in reply to Re: alarm not triggering SIGALRM on Windows 2003
in thread alarm not triggering SIGALRM on Windows 2003

From the perl -V command:

Summary of my perl5 (revision 5 version 8 subversion 4) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread : :

Replies are listed 'Best First'.
Re^3: alarm not triggering SIGALRM on Windows 2003
by desemondo (Hermit) on Sep 23, 2009 at 23:13 UTC
    I'd highly recommend you consider changing your Win2003 (production?) box to use the same Perl version as your winXP (development?) box.

    Not only will you run into little quirks with Perl itself (which it sounds like you already have) but you'll also run into quirks and differences in the Core Perl modules...

    Most module maintainers try to keep a fair amount of backward compatibility, but eventually the deprecated methods get turfed...
      The Perl version is the same on all three operating systems.
        Yeah that was just a hunch I had since I knew alarm() was relatively recently implemented in windows. It looks like you are correct and it just plain does not work correctly on Windows 2003 Server.