From: Georg Potthast 2 <nospam@georgpotthast.de>
To: Derek Johansen <djohanse678@gmail.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: telnetc behavior
Date: Mon, 20 Mar 2017 15:05:56 +0100 (CET) [thread overview]
Message-ID: <517558297.112296.1490018756653@webmail.strato.com> (raw)
In-Reply-To: <CAOv0vdkJsab1=XVi++wooUwe3zezztp5uQq5VftSzR13q6mCXQ@mail.gmail.com>
Derek,
maybe you try CTRL-M/CTRL-J instead of enter just for testing.
I never managed to generate a signal yet so I could not trigger that message. I tried CTRL-C for that.
You should enter CTRL-ALT-G to release the mouse from the Qemu window. Just CTRL-ALT will not do that and you probably send that signal to the TELNET server.
Georg
> Derek Johansen <djohanse678@gmail.com> hat am 20. März 2017 um 06:10 geschrieben:
>
>
> If I enter just one carriage return I never get a response from the server.
>
> I noticed something else. If I login as root, then do a ps command,
> the telnetd and ktcp processes are displayed as expected; I then
> mouse over and click in my QEMU/ELKS window, then do a ctrl-alt to
> exit mouse grab. I get a "signal received:2" message in the ELKS
> window, and my ktcp and telnetd ELKS processes no longer show up when
> I do the ps command. It looks like ctrl-alt is killing the ktcp and
> telnetd processes.
>
>
> On Sun, Mar 19, 2017 at 12:12 PM, Georg Potthast 2
> <nospam@georgpotthast.de> wrote:
> > 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@gmail.com> 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@vger.kernel.org
> >> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-03-20 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 5:23 telnetc behavior Derek Johansen
2017-03-19 18:12 ` Georg Potthast 2
2017-03-20 5:10 ` Derek Johansen
2017-03-20 14:05 ` Georg Potthast 2 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=517558297.112296.1490018756653@webmail.strato.com \
--to=nospam@georgpotthast.de \
--cc=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).