Re^2: Maximum length of commands in Net::Telnet package

No it's not the case. I have tested it on the command prompt on both AIX and SOLARIS and there is no truncation problem. In your case there might be some system configured limit.

Definitely a perl problem.

My theory is, syswrite isn't able to write the whole chunk. And in _put method it waits for response after syswrite. Because the command isn't complete there is no response and the command timesout. I am yet to verify this though.

I can give a temporary login if somebody is really willing to experiment it on my systems.

echo isn't the command we use in actual case. It was used for demo only.

I am available on yahoo IM as pspl_deba and on msn as debashish99@hotmail.com should some body be really willing to sort this out on chat.

Thanks and regards,

Debashish.

Comment on Re^2: Maximum length of commands in Net::Telnet package

Replies are listed 'Best First'.
Re^3: Maximum length of commands in Net::Telnet package by Anonymous Monk on Jun 10, 2004 at 15:39 UTC
Please do a little research before submitting something as a bug on rt.cpan.org. idsfa is correct - it has nothing to do with perl or Net::Telnet. This has been discussed before on comp.lang.perl.misc. http://groups.google.com/groups?as_umsgid=82u2iyo3s9.fsf%40shell2.shore.net Can you please close the bug you submitted? -- Jay Rogers	[reply]
Re^4: Maximum length of commands in Net::Telnet package by deba (Initiate) on Jun 11, 2004 at 04:43 UTC
Hi Jay, Thanks for taking time to look at it and pointing me to the link. We arrived at a similar work around to go ahead. I have pointed out before in this discussion, this may not be a problem of tty setting. I can type any number of characters as my command or it's parameter and get it executed on the native telnet connection. Am I missing something? The main reason of reporting it as a bug/ feature improvement is to have the code modified in the core module itself so that we won't have to write wrappers where ever we use it. In the worst case we can push this wrapper into the package itself so that the end user won't have a clue. The solution uses bash. What if my system doesn't have one? In our situation the scripts used csh. I have to do modifications at around a dozzne places to switch between bash and csh. Net::Telnet is a great package and we are using it at many places in our automation. But that doesn't mean we should stop improving it. We missed this bug before probably due to the assumption "tty setting is the culprit". Why not look at it more closely now? I won't close this bug unless I find a satisfying explanation. Thanks and regards Debashish.	[reply]