systemd-socket-proxyd
systemd
Developer
David
Strauss
david@davidstrauss.net
systemd-socket-proxyd
8
systemd-socket-proxyd
Bidirectionally proxy local sockets to another (possibly remote) socket.
systemd-socket-proxyd
OPTIONS
HOST:PORT
systemd-socket-proxyd
OPTIONS
UNIX-DOMAIN-SOCKET-PATH
Description
systemd-socket-proxyd is a generic
socket-activated network socket forwarder proxy daemon for IPv4,
IPv6 and UNIX stream sockets. It may be used to bi-directionally
forward traffic from a local listening socket to a local or remote
destination socket.
One use of this tool is to provide socket activation support
for services that do not natively support socket activation. On
behalf of the service to activate, the proxy inherits the socket
from systemd, accepts each client connection, opens a connection
to a configured server for each client, and then bidirectionally
forwards data between the two.
This utility's behavior is similar to
socat1.
The main differences for systemd-socket-proxyd
are support for socket activation with
Accept=false and an event-driven
design that scales better with the number of
connections.
Options
The following options are understood:
Exit status
On success, 0 is returned, a non-zero failure
code otherwise.
Examples
Simple Example
Use two services with a dependency and no namespace
isolation.
proxy-to-nginx.socket
proxy-to-nginx.service
nginx.conf
Enabling the proxy
Namespace Example
Similar as above, but runs the socket proxy and the main
service in the same private namespace, assuming that
nginx.service has
PrivateTmp= and
PrivateNetwork= set, too.
proxy-to-nginx.socket
proxy-to-nginx.service
nginx.conf
Enabling the proxy
See Also
systemd1,
systemd.socket5,
systemd.service5,
systemctl1,
socat1,
nginx1,
curl1