in reply to Net::Telnet core dumps

That's interesting that it actually core dumps. Can you load the core into a debugger and do a stack backtrace? Perhaps that would give you a clue, or at least something you could post somewhere?

The things that usually cause core dumps in Perl are, I think:

Signal handlers are buggy in Perl and they cause core dumps, quite often. And Net::Telnet is probably using SIGs to handle the timeouts, so... perhaps there's something to build on, there?

One other thing, related sort of to the second item in the above list: did you recently update/reinstall/rebuild your Perl?

Replies are listed 'Best First'.
RE: Re: Net::Telnet core dumps
by Anonymous Monk on Apr 20, 2000 at 00:01 UTC
    Didn't rebuild perl.
    Script is running on a SUN server with 4 processers, and over a gig of memory, with few users and notmany daemons, so it's not a memory issue
    I'll see if I can figure out how to examine the core in a debugger.
    Does anyone perhaps a more elegant solution for accomplishing what I'm trying to do than NET::Telnet?
      Well, you could always have the servers run the script regularly themselves (as a cronjob) and then have them email the results, or even telnet back. You could also have the main server email the remote servers to a specific account, and have the remote servers (assuming they can accept mail) run the backup program when mail from a certain name and IP arrives.

      P.S. Make a left bracket by typing [ and a right one by typing ]