Socketpipe connects over a TCP/IP socket a remote command to a local
input generation command and/or a local output processing command.
The connection is made by redirecting the input/output file descriptors
to the socket. This saves the context switching and data copying
overhead associated with piping data through ssh(1) or rsh(1).
Socketpipe must be installed on both machines and user authentication
is still performed by a command like ssh(1) or rsh(1). The
confidentiality and integrity of the data in transit is not protected
against malicious attacks; the command is designed for use in a
trusted LAN environment.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Remove more tags from pkg-descr files fo the form:
- Name
em@i.l
or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.
Update to 1.9:
Version 1.9 contains rather important band-aid for hanged socketpipe
instances in case of remote server crash.
PR: 123289
Submitted by: marck
Approved by: maintainer timeout (4 weeks)
Socketpipe connects over a TCP/IP socket a remote command to a local
input generation command and/or a local output processing command.
The connection is made by redirecting the input/output file descriptors
to the socket. This saves the context switching and data copying
overhead associated with piping data through ssh(1) or rsh(1).
Socketpipe must be installed on both machines and user authentication
is still performed by a command like ssh(1) or rsh(1). The
confidentiality and integrity of the data in transit is not protected
against mallicious attacks; the command is designed for use in a
trusted LAN environment.
Submitted by: dds
