Re: alarm not triggering SIGALRM on Windows 2003

Are you using an older version of perl on the Windows 2003 server? According to perlport for perl 5.8.0 alarm() was not implemented on Win32 systems.

But by perl 5.8.4 it appears to no longer be an portability issue.

Comment on Re: alarm not triggering SIGALRM on Windows 2003

Replies are listed 'Best First'.
Re^2: alarm not triggering SIGALRM on Windows 2003 by perlofwisdom (Pilgrim) on Sep 23, 2009 at 21:03 UTC
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 : :` [download]	[reply] [d/l]
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...	[reply]
Re^4: alarm not triggering SIGALRM on Windows 2003 by perlofwisdom (Pilgrim) on Sep 24, 2009 at 16:47 UTC
The Perl version is the same on all three operating systems.	[reply]
Re^5: alarm not triggering SIGALRM on Windows 2003 by thunders (Priest) on Sep 24, 2009 at 20:08 UTC