From 96c374d0a536286e18cad64d1b5ebb8f07c90334 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 18 Oct 2013 02:40:26 +0200 Subject: socket-proxyd: rename from saproxy The thing is a daemon, hence needs a "d" prefix. Also, we tend to not abbreviate names of background components unnecessarily, since they are not primary commands people type. Then, the fact that this thing does socket actviation is mostly in implementationd detail for the proxy. Also, do some minor indenting clean-ups and other code updates. --- man/systemd-saproxy.xml | 254 ------------------------------------------ man/systemd-socket-proxyd.xml | 254 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 254 insertions(+), 254 deletions(-) delete mode 100644 man/systemd-saproxy.xml create mode 100644 man/systemd-socket-proxyd.xml (limited to 'man') diff --git a/man/systemd-saproxy.xml b/man/systemd-saproxy.xml deleted file mode 100644 index ff8218c1e2..0000000000 --- a/man/systemd-saproxy.xml +++ /dev/null @@ -1,254 +0,0 @@ - - - - - - - systemd-saproxy - systemd - - - Developer - David - Strauss - david@davidstrauss.net - - - - - systemd-saproxy - 1 - - - systemd-saproxy - Inherit a socket. Bidirectionally - proxy. - - - - systemd-saproxy - OPTIONS - HOSTNAME-OR-IP - PORT-OR-SERVICE - - - systemd-saproxy - OPTIONS - UNIX-DOMAIN-SOCKET-PATH - - - - - Description - - systemd-saproxy provides a proxy - to socket-activate services that do not yet support - native socket activation. On behalf of the daemon, - the proxy inherits the socket from systemd, accepts - each client connection, opens a connection to the 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-saproxy - 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: - - - - - - Prints a short help - text and exits. - - - - - - Prints a version - string and exits. - - - - - - Skips verification of - the expected PID and file - descriptor numbers. Use if - invoked indirectly, for - example with a shell script - rather than with - - - - - - - - Exit status - On success 0 is returned, a non-zero failure - code otherwise. - - - Examples - - Direct-Use Example - Use two services with a dependency - and no namespace isolation. - - /etc/systemd/system/proxy-to-nginx.socket - - - - - - /etc/systemd/system/proxy-to-nginx.service - - - - - - /etc/nginx/nginx.conf - - - - - - - - - - - - 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 - - - - - - - - /etc/systemd/system/proxy-with-nginx.service - - - - - - - /usr/bin/saproxy-nginx.sh - - - - - - - /etc/nginx/nginx.conf - - - - - - - - - - - - - See Also - - - - systemd.service - 5 - , - - - systemd.socket - 5 - , - - systemctl - 1 - , - - socat - 1 - - - diff --git a/man/systemd-socket-proxyd.xml b/man/systemd-socket-proxyd.xml new file mode 100644 index 0000000000..90b3b1c3a4 --- /dev/null +++ b/man/systemd-socket-proxyd.xml @@ -0,0 +1,254 @@ + + + + + + + systemd-socket-proxyd + systemd + + + Developer + David + Strauss + david@davidstrauss.net + + + + + systemd-socket-proxyd + 1 + + + systemd-socket-proxyd + Inherit a socket. Bidirectionally + proxy. + + + + systemd-socket-proxyd + OPTIONS + HOSTNAME-OR-IP + PORT-OR-SERVICE + + + systemd-socket-proxyd + OPTIONS + UNIX-DOMAIN-SOCKET-PATH + + + + + Description + + systemd-socket-proxyd provides a proxy + to socket-activate services that do not yet support + native socket activation. On behalf of the daemon, + the proxy inherits the socket from systemd, accepts + each client connection, opens a connection to the 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: + + + + + + Prints a short help + text and exits. + + + + + + Prints a version + string and exits. + + + + + + Skips verification of + the expected PID and file + descriptor numbers. Use if + invoked indirectly, for + example with a shell script + rather than with + + + + + + + + Exit status + On success 0 is returned, a non-zero failure + code otherwise. + + + Examples + + Direct-Use Example + Use two services with a dependency + and no namespace isolation. + + /etc/systemd/system/proxy-to-nginx.socket + + + + + + /etc/systemd/system/proxy-to-nginx.service + + + + + + /etc/nginx/nginx.conf + + + + + + + + + + + + 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 + + + + + + + + /etc/systemd/system/proxy-with-nginx.service + + + + + + + /usr/bin/socket-proxyd-nginx.sh + + + + + + + /etc/nginx/nginx.conf + + + + + + + + + + + + + See Also + + + + systemd.service + 5 + , + + + systemd.socket + 5 + , + + systemctl + 1 + , + + socat + 1 + + + -- cgit v1.2.3-54-g00ecf