table of contents
other versions
- jessie 215-17+deb8u7
- jessie-backports 230-7~bpo8+2
- stretch 232-25+deb9u8
- testing 241-1
- stretch-backports 241-1~bpo9+1
- unstable 241-2
SYSTEMD-SOCKET-PROXYD(8) | systemd-socket-proxyd | SYSTEMD-SOCKET-PROXYD(8) |
NAME¶
systemd-socket-proxyd - Bidirectionally proxy local sockets to another (possibly remote) socket.SYNOPSIS¶
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 socat(1). 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: -h, --helpPrint a short help text and exit.
--version
Print a short version string and exit.
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. Example 1. proxy-to-nginx.socket[Socket] ListenStream=80 [Install] WantedBy=sockets.target
[Unit] Requires=nginx.service After=nginx.service [Service] ExecStart=/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock PrivateTmp=yes PrivateNetwork=yes
[...] server { listen unix:/tmp/nginx.sock; [...]
# systemctl enable proxy-to-nginx.socket # systemctl start proxy-to-nginx.socket $ curl http://localhost:80/
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. Example 5. proxy-to-nginx.socket[Socket] ListenStream=80 [Install] WantedBy=sockets.target
[Unit] Requires=nginx.service After=nginx.service JoinsNamespaceOf=nginx.service [Service] ExecStart=/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080 PrivateTmp=yes PrivateNetwork=yes
[...] server { listen 8080; [...]
# systemctl enable proxy-to-nginx.socket # systemctl start proxy-to-nginx.socket $ curl http://localhost:80/
SEE ALSO¶
systemd(1), systemd.socket(5), systemd.service(5), systemctl(1), socat(1), nginx(1), curl(1)systemd 230 |