Re: Sending and receiving data to standard input and output of the linux based server.

Thnaks for Information!! But the question is slight different. I can do either telnet, ssh or http daemon to connet to server and issue commands. I can even wait for the response. But all these assume that on the server side there is a standard command/shell prompt. My question is once I issue the command (eg ./run.out), this run.out waits for some <STDIN> and the prompt is ">>" instead of "# or $ or ~". The .out is now waiting for some data at the stdin, so I need to send some Data after it waits for STDIN. How to I Send data to the .out running at server waiting for the <STDIN>?

Comment on Re: Sending and receiving data to standard input and output of the linux based server.

Replies are listed 'Best First'.
Re^2: Sending and receiving data to standard input and output of the linux based server. by regexes (Hermit) on Mar 01, 2013 at 14:11 UTC
Basically, you need to know when the telnet/SSH session is prompting for input. How to get around that problem? Net::Telnet Make the prompt something you know, see here: Re: Net::Telent - How to get the prompt displayed after login using telnet? Then send the input, see here: Interactive input via telnet With Net::Telnet, it's all a matter of using cmd(), waitfor() and print() For SSH, you might try taking a look at Net::SSH::Expect I haven't searched here but I bet there's plenty of examples to be found.	[reply]
Re^2: Sending and receiving data to standard input and output of the linux based server. by tmharish (Friar) on Mar 01, 2013 at 13:36 UTC
SSH the file with params and redirect the input? `./run.out < file_with_params_SSHed_from_client > output_you_can_ssh_ba +ck_to_client` [download]	[reply] [d/l]
Re^2: Sending and receiving data to standard input and output of the linux based server. by hippo (Archbishop) on Mar 01, 2013 at 23:28 UTC
I can do either telnet, ssh or http Great - so use HTTP. These days web services are pretty trivial and you can use HTTPS for additional security and authentication. Simply send the server some data as query string or POST params and await the response. Let all the tricky interface stuff happen on the server side.	[reply]