gothic_mallard has asked for the wisdom of the Perl Monks concerning the following question:

Greetings fellow Monks.

My problem is thus:
I have a module that sends email by using Net::Telnet to make a connection to the server and then handle the transaction line-by-line. (I know Net::SMTP may be better for this, but I wrote it as a learning exercise.)

The thing is, the module appears to work correctly and the email is sent as required. However, ever since we have upgraded our servers to ActiveState Perl 5.6, it has continued to work, but is now printing the message:

PerlScript Error error '80004005' The Unsupported function alarm function is unimplemented at C:/Perl/si +te/lib/Net/Telnet.pm line 2023.

I'm certainly not calling this function explicitly and, as I said, this message did not appear prior to the Perl upgrade.

This is running in a Perlscript ASP environment on IIS with Perl 5.6 if that helps any.

Can anyone shed any light on the meaning of this error? Or what I might be doing wrong?

Thanks in advance.

J.

Replies are listed 'Best First'.
Re: "Unsupported function alarm function" with Net::Telnet problem
by Fletch (Bishop) on Nov 30, 2001 at 20:02 UTC

    According to perldoc perlport . . .

    alarm SECONDS alarm Not implemented. (Win32)

    It means just what it says: Net::Telnet tried to use alarm() but it's not available. It's trying to set things up to timeout after a certain period of time so that it won't hang indefinately if there's no reply.

      Thanks for the reply

      Why should it not be available? Is it part of the Net::Telnet module itself or something else that needs to be installed?

      If it isn't something that I can install, how can I solve this problem?

      Thanks again.

      J.

        Okay... looks like I got it sorted.

        Seems that even the docs for the latest PPM release of this module say that this feature is broken. ( I think it may run on UNIX, but not under NT )

        Got around it be reinstalling the older version that we were running previously - everything seems to be working fine now.

        Thanks again.

        J.