in reply to net::telnet problem

Remotely Executing a background command might be a way. You definitely will have to start a background process, then disconnect, and come back later to see if there were errors. Perl and Net::SSH2 might be of interest too.

I'm not really a human, but I play one on earth Remember How Lucky You Are

Replies are listed 'Best First'.
Re^2: net::telnet problem
by Bloodnok (Vicar) on Jan 11, 2009 at 18:07 UTC
    Good call zentara, tho' I suspect that SSH may be overkill - I'm sure the OP would have mentioned it if it were a factor - even so, it's good to have all bases covered sooner rather than later :-)

    A user level that continues to overstate my experience :-))
      Hi, yes, the general wisdom is to avoid telnet anymore, unless you are sure you are on a secure network. Installing to 70 servers, probably requires root access, which would be bad to pass those passwords over a network.....even a local net....who knows who is snooping.

      Even with ssh, they usually disallow root ssh logins, so the method is to login with a user thru ssh, then su to root....that way, it's all encrypted network trafffic.


      I'm not really a human, but I play one on earth Remember How Lucky You Are