Re: telnetc behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please try to use just one carriage return. The server expects to get one message and work on that. Not to get a message followed by an almost empty message immediately. I did not expect that to happen.

In the networking_guide I mentioned the commands I tried: e.g. whoami, pwd, echo 123

The server receives the output of a command from ELKS in chunks of 64 bytes. He may try to read new input from the remote side if there is a small pause after a chunk and get lost. Just wait till the prompt appears again before entering something new.

Georg


> Derek Johansen <djohanse678@xxxxxxxxx> hat am 19. März 2017 um 06:23 geschrieben:
> 
> 
> Using the new telnetc client on my host,
> 
> if I enter the lscommand  then 2 carriage returns, the first line of
> the output shows up in my telnet server:
> 
> ash banner basename cal cat chgr
> 
> The rest of the ls listing shows up in my telnet client, starting with
> the p from chgrp
> 
> When I enter env and enter 2 carriage returns in my client, it prints
> the environment variable (just one line) on the ELKS telnet server.  I
> would expect it to be sent to my client.
> 
> It looks like the first line of the telnet server output is not
> getting sent to the client in my configuration for some reason.
> 
> Thanks,
> Derek
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel]     [Linux ia64]     [DCCP]     [Linux for ARM]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux