Re: Where does the "prompt come from"
From: all mail refused (elvis_at_notatla.org.uk)
Date: 03/25/04
- Previous message: all mail refused: "Re: openssh 3.8p1 connect timeouts"
- In reply to: Niclas Bäckman: "Where does the "prompt come from""
- Next in thread: Per Hedeland: "Re: Where does the "prompt come from""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 25 Mar 2004 22:14:14 GMT
In article <c3s3b1$nf$1@newstree.wise.edt.ericsson.se>, Niclas Bäckman wrote:
>stdin/stdout/stderr from the ssh binary to a socket, and we then
>perform socket read/writes directly into the ssh tunnel. But when i perform
>a command, the prompt is never read up from the server.
>So it's difficult to know when a remote script is finished. Using the same
>solution but towards a telnet server always results in a prompt
>back to the client.
>
>I would be most greatful for any good ideas/hints in this case.
You can get the same when you overflow a buffer on a remote
program [1] and execute a non-login shell. A simple workaround is to
enter every command as
do_some -thing ; echo :::
and use the ":::" as a completion sign to the client program.
Really you want to investigate the conditions in which your shell
is running. Have a dig round in /proc for a problem shell and
a normal one to compare it to.
1. With permission of course.
-- Elvis Notargiacomo master AT barefaced DOT cheek
- Previous message: all mail refused: "Re: openssh 3.8p1 connect timeouts"
- In reply to: Niclas Bäckman: "Where does the "prompt come from""
- Next in thread: Per Hedeland: "Re: Where does the "prompt come from""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|