summaryrefslogtreecommitdiff
path: root/man/systemd-socket-activate.xml
blob: 5d7f157c72dd3b5c826feaf8267f89ccfa8a8bd6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
<?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*-->
<!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 Zbigniew Jędrzejewski-Szmek

  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://www.gnu.org/licenses/>.
-->

<refentry id="systemd-socket-activate"
          xmlns:xi="http://www.w3.org/2001/XInclude">

  <refentryinfo>
    <title>systemd-socket-activate</title>
    <productname>systemd</productname>

    <authorgroup>
      <author>
        <contrib>Developer</contrib>
        <firstname>Zbigniew</firstname>
        <surname>Jędrzejewski-Szmek</surname>
        <email>zbyszek@in.waw.pl</email>
      </author>
    </authorgroup>
  </refentryinfo>

  <refmeta>
    <refentrytitle>systemd-socket-activate</refentrytitle>
    <manvolnum>1</manvolnum>
  </refmeta>

  <refnamediv>
    <refname>systemd-socket-activate</refname>
    <refpurpose>Test socket activation of daemons</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <cmdsynopsis>
      <command>systemd-socket-activate</command>
      <arg choice="opt" rep="repeat">OPTIONS</arg>
      <arg choice="plain"><replaceable>daemon</replaceable></arg>
      <arg choice="opt" rep="repeat">OPTIONS</arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para><command>systemd-socket-activate</command> may be used to launch a socket-activated service binary from the command
    line for testing purposes. It may also be used to launch individual instances of the service binary per connection.
    </para>

    <para>The daemon to launch and its options should be specified
    after options intended for <command>systemd-socket-activate</command>.
    </para>

    <para>If the <option>--inetd</option> option is given, the socket file descriptor will be used as the standard
    input and output of the launched process. Otherwise, standard input and output will be inherited, and sockets will
    be passed through file descriptors 3 and higher. Sockets passed through <varname>$LISTEN_FDS</varname> to
    <command>systemd-socket-activate</command> will be passed through to the daemon, in the original positions. Other sockets
    specified with <option>--listen=</option> will use consecutive descriptors.  By default,
    <command>systemd-socket-activate</command> listens on a stream socket, use <option>--datagram</option> and
    <option>--seqpacket</option> to listen on datagram or sequential packet sockets instead (see below).
    </para>
  </refsect1>

  <refsect1>
    <title>Options</title>
    <variablelist>
      <varlistentry>
        <term><option>-l <replaceable>address</replaceable></option></term>
        <term><option>--listen=<replaceable>address</replaceable></option></term>

        <listitem><para>Listen on this <replaceable>address</replaceable>.
        Takes a string like <literal>2000</literal> or
        <literal>127.0.0.1:2001</literal>.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-a</option></term>
        <term><option>--accept</option></term>

        <listitem><para>Launch an instance of the service binary for each connection and pass the connection
        socket.</para></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-d</option></term>
        <term><option>--datagram</option></term>

        <listitem><para>Listen on a datagram socket (<constant>SOCK_DGRAM</constant>), instead of a stream socket
        (<constant>SOCK_STREAM</constant>). May not be combined with <option>--seqpacket</option>.</para></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--seqpacket</option></term>

        <listitem><para>Listen on a sequential packet socket (<constant>SOCK_SEQPACKET</constant>), instead of a stream
        socket (<constant>SOCK_STREAM</constant>). May not be combined with
        <option>--datagram</option>.</para></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--inetd</option></term>

        <listitem><para>Use the inetd protocol for passing file descriptors, i.e. as standard input and standard
        output, instead of the new-style protocol for passing file descriptors using <varname>$LISTEN_FDS</varname>
        (see above).</para></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-E <replaceable>VAR</replaceable><optional>=<replaceable>VALUE</replaceable></optional></option></term>
        <term><option>--setenv=<replaceable>VAR</replaceable><optional>=<replaceable>VALUE</replaceable></optional></option></term>

        <listitem><para>Add this variable to the environment of the
        launched process. If <replaceable>VAR</replaceable> is
        followed by <literal>=</literal>, assume that it is a
        variable–value pair. Otherwise, obtain the value from the
        environment of <command>systemd-socket-activate</command> itself.
        </para></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--fdname=</option><replaceable>NAME</replaceable><optional>:<replaceable>NAME</replaceable>...</optional></term>

        <listitem><para>Specify names for the file descriptors passed. This is equivalent to setting
        <varname>FileDescriptorName=</varname> in socket unit files, and enables use of
        <citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
        Multiple entries may be specifies using separate options or by separating names with colons
        (<literal>:</literal>) in one option. In case more names are given than descriptors, superflous ones willl be
        ignored. In case less names are given than descriptors, the remaining file descriptors will be unnamed.
        </para></listitem>
      </varlistentry>

      <xi:include href="standard-options.xml" xpointer="help" />
      <xi:include href="standard-options.xml" xpointer="version" />
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Environment variables</title>
    <variablelist class='environment-variables'>
      <varlistentry>
        <term><varname>$LISTEN_FDS</varname></term>
        <term><varname>$LISTEN_PID</varname></term>
        <term><varname>$LISTEN_FDNAMES</varname></term>

        <listitem><para>See
        <citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para></listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>$SYSTEMD_LOG_TARGET</varname></term>
        <term><varname>$SYSTEMD_LOG_LEVEL</varname></term>
        <term><varname>$SYSTEMD_LOG_COLOR</varname></term>
        <term><varname>$SYSTEMD_LOG_LOCATION</varname></term>

        <listitem><para>Same as in
        <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para></listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Examples</title>

    <example>
      <title>Run an echo server on port 2000</title>

      <programlisting>$ systemd-socket-activate -l 2000 --inetd -a cat</programlisting>
    </example>

    <example>
      <title>Run a socket-activated instance of <citerefentry><refentrytitle>systemd-journal-gatewayd</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>

      <programlisting>$ systemd-socket-activate -l 19531 /usr/lib/systemd/systemd-journal-gatewayd</programlisting>
    </example>
  </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>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
      <citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
      <citerefentry project='man-pages'><refentrytitle>cat</refentrytitle><manvolnum>1</manvolnum></citerefentry>
    </para>
  </refsect1>
</refentry>