Connects the input/output of a remote process with local programs
'Socketpipe' directly connects the input/output of a remote process with local programs over a TCP/IP socket. Although the initial communication setup is performed through client-server intermediaries such as SSH or RSH, the communication channel that socketpipe establishes is a direct socket connection between the local and the remote processes, similar to a local pipe. The use of socketpipe removes the inefficiency of multiple data copies and context switches through RSH/SSH, and can in many cases offer dramatic throughput improvements.
DocumentationUser manpage avilable in HTML format from http://www.spinellis.gr/sw/unix/socketpipe/socketpipe.html; User manpage avilable in PDF format from http://www.spinellis.gr/sw/unix/socketpipe/socketpipe.pdf
released on 6 December 2015
1 April 2004
Leaders and contributors
Resources and communication
This entry (in part or in whole) was last reviewed on 14 January 2017.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.