Linux Today: Linux News On Internet Time.
Search Linux Today
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Server Daily
IT Management Daily
Subscribe News
Subscribe PR
Subscribe Security

internet.com
Internet News
Small Business

Advertise
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Controlling Liquor Loss with Linux

Chrome Web Browser Finally Comes to Android Phones, Tablets

The Best Cloud Music Options for the Linux Desktop

The Secret to Red Hat's Billion-Dollar Success: Everyone's The Boss

NGINX Adds Support for Open Source Web Server

SUSE hits the big 2-0

A Look at 3D Printing and Open Source

Creating a vDSO: the Colonel's Other Chicken

LibreOffice developer shows prototype Android and HTML5 ports

Facebook is a surveillance engine, not friend: Richard Stallman, Free Software Foundation



Applications Management Engineer Sr (NYC)
Next Step Systems
US-NY-New York

Justtechjobs.com Post A Job | Post A Resume
:Names Pipes... or how to get two separate applications to interact
Names Pipes... or how to get two separate applications to interact
Jun 30, 2009, 07 :32 UTC (0 Talkback[s]) (4694 reads)

(Other stories by Edmundo Carmona)

[ Thanks to Edmundo for this link. ]

"Great. However, I didn't' want to connect to a host with one openSSH service. I had to connect to a router (a HW router, so to speak) that, whenever I sent it more than one command, would break my connection.

"After several tries and experiments, I thought about creating one application that would use the ssh client to send commands to the router and get the output of the ssh client. It would wait for the router's prompt to show up before sending another command. Now, that would require not only getting the output of the ssh client, as that is a piece of cake:

$ ssh user@host | ./ssh_handler"

Complete Story

Related Stories:
6 things that I miss in bash(Jun 09, 2009)
Use the Bash trap Statement to Clean Up Temporary Files(May 12, 2009)
The Bash declare Statement(Apr 29, 2009)
More Linux tips every geek should know(Apr 10, 2009)
lsof Seeks All Open Files(Apr 08, 2009)
Exploring filters and pipes(Apr 02, 2009)
Linux tips every geek should know(Mar 02, 2009)
pv (Pipe Viewer) - Shell pipeline element to meter data passing through(Dec 30, 2008)
Things You Should Never EVER Type in Linux. Ever!(Aug 29, 2008)
Review: Bash Cookbook(Aug 13, 2008)
Regular Expressions and Search Patterns(Sep 25, 2007)
Network Card Bonding On CentOS(Jul 06, 2007)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!

..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP