Thank you for you quickly response thanos!
I have updates... first of all, my fellow monk, apologizes this young grasshopper. My command line have a lot of e-mails, and I forgot to escape them in my test script. So part of the problem is solved: the "More? " is coming in the result, and the waitfor is working. NICE.
However, in the ideal world, I shouldn't be concerned about a command line with 1024 chars limitation, this is awkward. The "More? " shouldn't NEVER be asked... So I'm opened to ideas that fix this. So I checked the max_buffer_length and returned its default value: 1048576 bytes, 1 MiB. Well, I'm not sure, but I suspect this behavior should be on server side.
Regarding about why telnet, your're absolutely right. AFAIK, the best option should be SSH. But this server is maintained by another team, I'll ask them if it is possible to change to SSH. Thanks for minding about this.
I'm still working on print and waitfor... updates will come.
In reply to Re^2: Telnet command with more than 1024 chars (updated)
by ElectricCheese
in thread Telnet command with more than 1024 chars
by ElectricCheese
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |