Names Pipes... or how to get two separate applications to interact
Jun 30, 2009, 07:32 (0 Talkback[s])
(Other stories by Edmundo Carmona)
WEBINAR:
On-Demand
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
[ 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 10, 2009)
- Use the Bash trap Statement to Clean Up Temporary Files(May 13, 2009)
- The Bash declare Statement(Apr 30, 2009)
- lsof Seeks All Open Files(Apr 08, 2009)
- Exploring filters and pipes(Apr 02, 2009)
- Linux tips every geek should know(Mar 03, 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 14, 2008)
- Regular Expressions and Search Patterns(Sep 25, 2007)
- Network Card Bonding On CentOS(Jul 06, 2007)
