-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partial output of remote telnet to local console #211
Comments
I can confirm that I have seen this behavior a number of times during recent testing.
|
The observed bad behaviour is coming from a poor redirection implementation in First is that I also had to disable |
Cleanup of telnetd client loop. Restore select for PTY master side. Correct read / write behavior for PTY master side: can return without blocking if less data available in buffer than requested by the user. Fixes ghaerr#211
Server and PTY master side fixed. But the current implementation of |
While testing the fix to the
select()
weakness (see #208), I can observe a problem that looks closely linked to the one reported by @Mellvik in issue #133 about the console management.I am using
busybox telnet 127.0.0.1 2323
on the host and QEMU for ELKS target, with onlyktcp
andtelnetd
daemons. Sometimes part of the output of the remote command is directed to the ELKS console in QEMU, and not to the remote telnet client, even if not logged in !In remote telnet client:
And in local console (in QEMU):
Here, the beginning of the
ls -l
command output goes to the local console, then the remaining goes to the remote telnet client.The text was updated successfully, but these errors were encountered: