socket-event(8) [debian man page]

socket-event(8) 					      System Manager's Manual						   socket-event(8)

NAME

       socket - event signalling that a socket connection has been made

SYNOPSIS

       socket PROTO=PROTO PORT=PORT ADDR=ADDR

       socket PROTO=PROTO PATH=PATH

DESCRIPTION

       The  socket event is generated by the upstart-socket-bridge(8) daemon when a socket connection is made whose details match the socket event
       condition and environment specified in a jobs start on or stop on stanza.

       When an incoming connection is detected, the file descriptor representing the socket is passed to the  job  in  question  to  allow  it	to
       accept(2) the connection. Additionally, the environment variable UPSTART_JOB will contain the name of the event ("socket") and the environ-
       ment variable UPSTART_FDS will contain the number of the file descriptor corresponding to the listening socket.

EXAMPLES

   Internet socket
       Start web server when first client connects from localhost:

	      start on socket PROTO=inet PORT=80 ADDR=127.0.0.1

   Local socket
	      start on socket PROTO=unix PATH=/var/run/.s.pgsql.1234

   Abstract socket
	      start on socket PROTO=unix PATH=@/at/upstart/example

AUTHOR

       Written by Scott James Remnant <scott@netsplit.com>

       Manual page written by James Hunt <james.hunt@ubuntu.com>

BUGS

       Report bugs at <https://launchpad.net/upstart/+bugs>

COPYRIGHT

       Copyright (C) 2011 Canonical Ltd.

       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

SEE ALSO

       init(5) init(8) socket(2) socket(7) upstart-socket-bridge(8)

upstart 							    2011-03-08							   socket-event(8)

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, --help
	   Print a short help text and exit.

       --version
	   Print a short version string and exit.

       --connections-max=, -c
	   Sets the maximum number of simultaneous connections, defaults to 256. If the limit of concurrent connections is reached further
	   connections will be refused.

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

       Example 2. proxy-to-nginx.service

	   [Unit]
	   Requires=nginx.service
	   After=nginx.service
	   Requires=proxy-to-nginx.socket
	   After=proxy-to-nginx.socket

	   [Service]
	   ExecStart=/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock
	   PrivateTmp=yes
	   PrivateNetwork=yes

       Example 3. nginx.conf

	   [...]
	   server {
	       listen	    unix:/tmp/nginx.sock;
	       [...]

       Example 4. Enabling the proxy

	   # systemctl enable --now 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

       Example 6. proxy-to-nginx.service

	   [Unit]
	   Requires=nginx.service
	   After=nginx.service
	   Requires=proxy-to-nginx.socket
	   After=proxy-to-nginx.socket
	   JoinsNamespaceOf=nginx.service

	   [Service]
	   ExecStart=/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080
	   PrivateTmp=yes
	   PrivateNetwork=yes

       Example 7. nginx.conf

	   [...]
	   server {
	       listen	    8080;
	       [...]

       Example 8. Enabling the proxy

	   # systemctl enable --now 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 237														  SYSTEMD-SOCKET-PROXYD(8)