Limit of command line in telnet client

[Suriao Jr, Eloi]

When I connect to um second host from a Unix Tru64 using telnet client, I cant use more that 512 caracters in command line.

When I do the same connect from a Windows using telnet or others telnet clients like Putty or Teraterm, the limit of the 512 caracters does not exist.

How I do to use more than 512 caracters in the same command line?

Im using Compaq Tru64 UNIX V5.1B (Rev. 2650).

[Ivan Ferreira]

I think that I don't understand well the problem but you can try setting the COLUMNS environment variable.

COLUMNS=1024
export COLUMNS


Or

export COLUMNS=1024

[Joris Denayer]

Hi,

Indeed, the maximum command length seems to be 512.

Did you try
# this is a very long \
> command line. I type \
> a backslash to continue\
> on the next line.

Anyway, you'll bump against shell-limits after this limit.

[Suriao Jr, Eloi]

The second host is not a shell unix, is a Ericsson application.
I think that the telnet client open telnet session in LINEMODE and the restriction is because edit buffer!

The command "export COLUMNS=1024" before open telnet not works.

Slash(\) caracter dont work too, because isnt a shell.

[Suriao Jr, Eloi]

More information from telnet:
(RJODIG907:bscstim) $ telnet
telnet> set escape ^Y
escape character is '^Y'.
telnet> open 192.168.1.1 1234
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^Y'.
CONNECTING TO CAI...

PROCESS xpto1234 CONNECTED...

Enter command: ^Y
telnet> status
Connected to 10.112.56.41.
Operating in obsolete linemode
Local character echo
Escape character is '^Y'.
^Y
telnet> display
will flush output when sending interrupt characters.
won't send interrupt characters in urgent mode.
won't send login name and/or authentication information.
won't map carriage return on output.
will recognize certain control characters.
won't turn on socket level debugging.
won't print hexadecimal representation of network traffic.
won't print user readable output for "netdata".
won't show option processing.
won't print hexadecimal representation of terminal traffic.

echo [^E]
escape [^Y]
tracefile "(standard output)"
flushoutput [^O]
interrupt [^C]
quit [^\]
eof [^D]
erase [^H]
kill [^U]
lnext [^V]
susp [^Z]
reprint [^R]
worderase [^W]
start [^Q]
stop [^S]
forw1 [off]
forw2 [off]

The connected host is operating in obsolete linemode. I think that restriction of length is in the buffer.

[Suriao Jr, Eloi]

I resolved using "mode character" after connected.

I have a second problem that telnet server not accept RETURN Key (chr 13), only Ctrl+J combinations keys (chr 10).

[Suriao Jr, Eloi]

I resolved using "mode character" after connected.