X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-socket-proxyd.xml;h=ab80a2b4ba17de823b538d037260907fc419d52d;hp=fcf4aafd60d2d5df9081a5bdffb753c3df581404;hb=93ae25e6fd62b2f87c3dd9ad3e81934eecc48057;hpb=8569a77629949b7818d00eba8eea1d05e2d1fc32 diff --git a/man/systemd-socket-proxyd.xml b/man/systemd-socket-proxyd.xml index fcf4aafd6..ab80a2b4b 100644 --- a/man/systemd-socket-proxyd.xml +++ b/man/systemd-socket-proxyd.xml @@ -20,7 +20,9 @@ You should have received a copy of the GNU Lesser General Public License along with systemd; If not, see . --> - + + systemd-socket-proxyd systemd @@ -35,7 +37,7 @@ systemd-socket-proxyd - 1 + 8 systemd-socket-proxyd @@ -59,12 +61,12 @@ systemd-socket-proxyd is a generic socket-activated network socket forwarder proxy daemon - for IPV4, IPv6 and UNIX stream sockets. It may be used + 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 + 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 @@ -83,21 +85,8 @@ Options The following options are understood: - - - - - Prints a short help - text and exits. - - - - - - Prints a version - string and exits. - - + + @@ -108,34 +97,30 @@ Examples - Direct-Use Example + Simple Example Use two services with a dependency and no namespace isolation. - - /etc/systemd/system/proxy-to-nginx.socket - - + proxy-to-nginx.socket + - +WantedBy=sockets.target]]> - - /etc/systemd/system/proxy-to-nginx.service - - + proxy-to-nginx.service + - +ExecStart=/usr/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock +PrivateTmp=yes +PrivateNetwork=yes]]> - - /etc/nginx/nginx.conf + + nginx.conf - - - + Enabling the proxy + - +$ curl http://localhost:80/]]> - Indirect-Use Example - Use a shell script to isolate the - service and proxy into the same namespace. - This is particularly useful for running - TCP-only daemons without the daemon - affecting ports on regular - interfaces. - - - - /etc/systemd/system/proxy-with-nginx.socket - -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 + - +WantedBy=sockets.target]]> - - - - /etc/systemd/system/proxy-with-nginx.service - - + proxy-to-nginx.service + - +ExecStart=/usr/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080 +PrivateTmp=yes +PrivateNetwork=yes]]> - - - /usr/bin/socket-proxyd-nginx.sh - - - - - - - /etc/nginx/nginx.conf - - + nginx.conf + - + [...]]]> - - - - + + Enabling the proxy + @@ -228,7 +187,9 @@ $ curl http://localhost:80/]]> systemd.socket5, systemd.service5, systemctl1, - socat1 + socat1, + nginx1, + curl1