If the offending code is in both releases, doesn't that imply that it is not called in
the standard release? I have the latest standard release installed on Win2K, and
everything is working OK except for renewals. The SF version emits the SIGALRM error.
I do have a problem with renewals timing out in the standard code, I haven't traced
the problem yet.
John W Roche
eInfosystems.net
>From Paul:
<snip>
He is correct, but I don't think it will solve the compatibility
problem, since ActiveState perl doesn't support the alarm() function
and does not define the POSIX macro SIGALRM...
> > The portability problem should not be unique to the SF code. On line
> > 242 of the module OPS.pm in version 2.49 of the supported code:
> >
> > sigaction SIGALRM, new POSIX::SigAction( 'OPS::alrm_handler' );
> > alarm( $timeout );
> >
> > On line 164 of the module OPS::Sock of version 1.53 of the SF code:
> >
> > sigaction SIGALRM, new POSIX::SigAction('Sock::alrm_handler');
> > return alarm($timeout);
>
