2013-10-15 03:41:47 +04:00
<?xml version="1.0"?>
<!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2013 David Strauss
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2014-02-13 23:33:51 +04:00
<refentry id= "systemd-socket-proxyd"
2015-02-04 05:14:13 +03:00
xmlns:xi="http://www.w3.org/2001/XInclude">
2014-02-13 23:33:51 +04:00
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd-socket-proxyd</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > David</firstname>
<surname > Strauss</surname>
<email > david@davidstrauss.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-socket-proxyd</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-socket-proxyd</refname>
<refpurpose > Bidirectionally proxy local sockets to another (possibly remote) socket.</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
<command > systemd-socket-proxyd</command>
<arg choice= "opt" rep= "repeat" > <replaceable > OPTIONS</replaceable> </arg>
<arg choice= "plain" > <replaceable > HOST</replaceable> :<replaceable > PORT</replaceable> </arg>
</cmdsynopsis>
<cmdsynopsis >
<command > systemd-socket-proxyd</command>
<arg choice= "opt" rep= "repeat" > <replaceable > OPTIONS</replaceable> </arg>
<arg choice= "plain" > <replaceable > UNIX-DOMAIN-SOCKET-PATH</replaceable>
</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para >
<command > systemd-socket-proxyd</command> 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.</para>
2013-11-07 01:40:54 +04:00
2015-02-04 05:14:13 +03:00
<para > 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.</para>
<para > This utility's behavior is similar to
2015-03-14 05:22:39 +03:00
<citerefentry project= 'die-net' > <refentrytitle > socat</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> .
2015-02-04 05:14:13 +03:00
The main differences for <command > systemd-socket-proxyd</command>
are support for socket activation with
<literal > Accept=false</literal> and an event-driven
design that scales better with the number of
connections.</para>
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<xi:include href= "standard-options.xml" xpointer= "help" />
<xi:include href= "standard-options.xml" xpointer= "version" />
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
<para > On success, 0 is returned, a non-zero failure
code otherwise.</para>
</refsect1>
<refsect1 >
<title > Examples</title>
<refsect2 >
<title > Simple Example</title>
<para > Use two services with a dependency and no namespace
isolation.</para>
<example >
<title > proxy-to-nginx.socket</title>
<programlisting > < ![CDATA[[Socket]
2013-10-15 03:41:47 +04:00
ListenStream=80
[Install]
2014-02-14 18:56:19 +04:00
WantedBy=sockets.target]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > proxy-to-nginx.service</title>
<programlisting > < ![CDATA[[Unit]
2013-10-15 03:41:47 +04:00
Requires=nginx.service
2013-11-28 00:14:08 +04:00
After=nginx.service
2013-10-15 03:41:47 +04:00
[Service]
2013-11-28 00:14:08 +04:00
ExecStart=/usr/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock
PrivateTmp=yes
2014-02-14 18:56:19 +04:00
PrivateNetwork=yes]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > nginx.conf</title>
<programlisting >
2013-10-15 03:41:47 +04:00
< ![CDATA[[...]
server {
listen unix:/tmp/nginx.sock;
[...]]]>
</programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > Enabling the proxy</title>
<programlisting > < ![CDATA[# systemctl enable proxy-to-nginx.socket
2013-10-22 03:50:49 +04:00
# systemctl start proxy-to-nginx.socket
2014-02-14 18:56:19 +04:00
$ curl http://localhost:80/]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
</refsect2>
<refsect2 >
<title > Namespace Example</title>
<para > Similar as above, but runs the socket proxy and the main
service in the same private namespace, assuming that
<filename > nginx.service</filename> has
<varname > PrivateTmp=</varname> and
<varname > PrivateNetwork=</varname> set, too.</para>
<example >
<title > proxy-to-nginx.socket</title>
<programlisting > < ![CDATA[[Socket]
2013-10-15 03:41:47 +04:00
ListenStream=80
[Install]
2014-02-14 18:56:19 +04:00
WantedBy=sockets.target]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > proxy-to-nginx.service</title>
<programlisting > < ![CDATA[[Unit]
2013-11-28 00:14:08 +04:00
Requires=nginx.service
After=nginx.service
JoinsNamespaceOf=nginx.service
2013-10-15 03:41:47 +04:00
[Service]
2013-11-28 00:14:08 +04:00
ExecStart=/usr/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080
PrivateTmp=yes
2014-02-14 18:56:19 +04:00
PrivateNetwork=yes]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > nginx.conf</title>
<programlisting > < ![CDATA[[...]
2013-10-15 03:41:47 +04:00
server {
listen 8080;
2014-02-14 18:56:19 +04:00
[...]]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
<title > Enabling the proxy</title>
<programlisting > < ![CDATA[# systemctl enable proxy-to-nginx.socket
2013-11-28 00:14:08 +04:00
# systemctl start proxy-to-nginx.socket
2014-02-14 18:56:19 +04:00
$ curl http://localhost:80/]]></programlisting>
2015-02-04 05:14:13 +03:00
</example>
</refsect2>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2015-03-14 05:22:39 +03:00
<citerefentry project= 'die-net' > <refentrytitle > socat</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry project= 'die-net' > <refentrytitle > nginx</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry project= 'die-net' > <refentrytitle > curl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
</para>
</refsect1>
2013-10-15 03:41:47 +04:00
</refentry>