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
linenoise eats a serial port #38
Comments
Hello, what kind of operating system and terminal are you using in your ARM device? What is the value of $TERM? Thanks. |
Hi, thanks for looking into it. This is an OpenEmbedded-based distro, Yocto Project's "Danny" branch. I have recently posted a set of patches there to be able to build redis, but ran into this issue. The platform is armv7a-vfp-neon / TI OMAP3730. TERM is 'linux' on the serial console, and TERM is 'xterm' through ssh (from an ubuntu screen.) |
A recipe for Redis 2.6.9, an advanced key-value store. Needed some patching of Makefiles and deps to get it to work with OE. OE Specific configuration: This is built to override MALLOC and use libc's malloc instead of the provided jemalloc or tcmalloc that weren't building correctly. Also the default savepoint setting was updated in the default redis.conf to tune for a small embedded system. Known Bug: redis-cli eats all the input on a serial port - watch out when using the serial console with redis-cli. see antirez/linenoise#38 Tested with Yocto "Danny" / armv7a. Signed-off-by: Kevin Baker <kevinb@ventureresearch.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Hello, I've the feeling I fixed this in recent commits (see commit 01cd117). Please could you retest? Thanks. |
Works fine in redis 2.6.9... however after some updates to the yocto OS, TERM is now xterm on both serial console and SSH. Closing. |
Using redis on an ARM embedded-system; however, when opening redis-cli on the serial console, I cannot see any characters, and also input doesn't seem to work, as typing commands blind doesn't do anything either.
Also, all control signals are consumed as well so I have to kill off the process to get control of the serial port back.
Using redis-cli over SSH to the same device works fine. After logging in I see there is a .rediscli-history file that has the commands that I was typing over SSH, but nothing for the serial port.
The text was updated successfully, but these errors were encountered: