|
Lines 149-278
Link Here
|
| 149 |
|
149 |
|
| 150 |
<para>Additionally, different command-line options can be passed |
150 |
<para>Additionally, different command-line options can be passed |
| 151 |
to <application>inetd</application> via the |
151 |
to <application>inetd</application> via the |
| 152 |
<literal>inetd_flags</literal> option.</para> |
152 |
<literal>inetd_flags</literal> option. By default, |
| 153 |
</sect2> |
|
|
| 154 |
|
| 155 |
<sect2 id="network-inetd-cmdline"> |
| 156 |
<title>Command-Line Options</title> |
| 157 |
|
| 158 |
<para><application>inetd</application> synopsis:</para> |
| 159 |
|
| 160 |
<para><option> inetd [-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address | hostname] |
| 161 |
[-p filename] [-R rate] [configuration file]</option></para> |
| 162 |
|
| 163 |
<variablelist> |
| 164 |
<varlistentry> |
| 165 |
<term>-d</term> |
| 166 |
|
| 167 |
<listitem> |
| 168 |
<para>Turn on debugging.</para> |
| 169 |
</listitem> |
| 170 |
</varlistentry> |
| 171 |
|
| 172 |
<varlistentry> |
| 173 |
<term>-l</term> |
| 174 |
|
| 175 |
<listitem> |
| 176 |
<para>Turn on logging of successful connections.</para> |
| 177 |
</listitem> |
| 178 |
</varlistentry> |
| 179 |
|
| 180 |
<varlistentry> |
| 181 |
<term>-w</term> |
| 182 |
|
| 183 |
<listitem> |
| 184 |
<para>Turn on TCP Wrapping for external services (on by |
| 185 |
default).</para> |
| 186 |
</listitem> |
| 187 |
</varlistentry> |
| 188 |
|
| 189 |
<varlistentry> |
| 190 |
<term>-W</term> |
| 191 |
|
| 192 |
<listitem> |
| 193 |
<para>Turn on TCP Wrapping for internal services which are |
| 194 |
built into <application>inetd</application> (on by |
| 195 |
default).</para> |
| 196 |
</listitem> |
| 197 |
</varlistentry> |
| 198 |
|
| 199 |
<varlistentry> |
| 200 |
<term>-c maximum</term> |
| 201 |
|
| 202 |
<listitem> |
| 203 |
<para>Specify the default maximum number of simultaneous |
| 204 |
invocations of each service; the default is unlimited. |
| 205 |
May be overridden on a per-service basis with the |
| 206 |
<option>max-child</option> parameter.</para> |
| 207 |
</listitem> |
| 208 |
</varlistentry> |
| 209 |
|
| 210 |
<varlistentry> |
| 211 |
<term>-C rate</term> |
| 212 |
|
| 213 |
<listitem> |
| 214 |
<para>Specify the default maximum number of times a |
| 215 |
service can be invoked from a single IP address in one |
| 216 |
minute; the default is unlimited. May be overridden on a |
| 217 |
per-service basis with the |
| 218 |
<option>max-connections-per-ip-per-minute</option> |
| 219 |
parameter.</para> |
| 220 |
</listitem> |
| 221 |
</varlistentry> |
| 222 |
|
| 223 |
<varlistentry> |
| 224 |
<term>-R rate</term> |
| 225 |
|
| 226 |
<listitem> |
| 227 |
<para>Specify the maximum number of times a service can be |
| 228 |
invoked in one minute; the default is 256. A rate of 0 |
| 229 |
allows an unlimited number of invocations.</para> |
| 230 |
</listitem> |
| 231 |
</varlistentry> |
| 232 |
|
| 233 |
<varlistentry> |
| 234 |
<term>-a</term> |
| 235 |
|
| 236 |
<listitem> |
| 237 |
<para>Specify one specific IP address to bind to. |
| 238 |
Alternatively, a hostname can be specified, in which case |
| 239 |
the IPv4 or IPv6 address which corresponds to that |
| 240 |
hostname is used. Usually a hostname is specified when |
| 241 |
<application>inetd</application> is run inside a |
| 242 |
&man.jail.8;, in which case the hostname corresponds to |
| 243 |
the &man.jail.8; environment.</para> |
| 244 |
|
| 245 |
<para>When hostname specification is used and both IPv4 |
| 246 |
and IPv6 bindings are desired, one entry with the |
| 247 |
appropriate protocol type for each binding is required |
| 248 |
for each service in |
| 249 |
<filename>/etc/inetd.conf</filename>. For example, a |
| 250 |
TCP-based service would need two entries, one using |
| 251 |
<literal>tcp4</literal> for the protocol and the other |
| 252 |
using <literal>tcp6</literal>.</para> |
| 253 |
</listitem> |
| 254 |
</varlistentry> |
| 255 |
|
| 256 |
<varlistentry> |
| 257 |
<term>-p</term> |
| 258 |
|
| 259 |
<listitem> |
| 260 |
<para>Specify an alternate file in which to store the |
| 261 |
process ID.</para> |
| 262 |
</listitem> |
| 263 |
</varlistentry> |
| 264 |
</variablelist> |
| 265 |
|
| 266 |
<para>These options can be passed to |
| 267 |
<application>inetd</application> using the |
| 268 |
<literal>inetd_flags</literal> option in |
| 269 |
<filename>/etc/rc.conf</filename>. By default, |
| 270 |
<literal>inetd_flags</literal> is set to |
153 |
<literal>inetd_flags</literal> is set to |
| 271 |
<literal>-wW</literal>, which turns on TCP wrapping for |
154 |
<literal>-wW</literal>, which turns on TCP wrapping for |
| 272 |
<application>inetd</application>'s internal and external |
155 |
<application>inetd</application>'s internal and external |
| 273 |
services. For novice users, these parameters usually do not |
156 |
services. For novice users, these parameters usually do not |
| 274 |
need to be modified or even entered in |
157 |
need to be modified or even entered in |
| 275 |
<filename>/etc/rc.conf</filename>.</para> |
158 |
<filename>/etc/rc.conf</filename>. Other options with their |
|
|
159 |
detailed descriptions can be found in the &man.inetd.8; manual |
| 160 |
page.</para> |
| 276 |
|
161 |
|
| 277 |
<note> |
162 |
<note> |
| 278 |
<para>An external service is a daemon outside of |
163 |
<para>An external service is a daemon outside of |
|
Lines 282-288
Link Here
|
| 282 |
<application>inetd</application> has the facility of |
167 |
<application>inetd</application> has the facility of |
| 283 |
offering within itself.</para> |
168 |
offering within itself.</para> |
| 284 |
</note> |
169 |
</note> |
| 285 |
|
|
|
| 286 |
</sect2> |
170 |
</sect2> |
| 287 |
|
171 |
|
| 288 |
<sect2 id="network-inetd-conf"> |
172 |
<sect2 id="network-inetd-conf"> |
|
Lines 292-307
Link Here
|
| 292 |
controlled through the <filename>/etc/inetd.conf</filename> |
176 |
controlled through the <filename>/etc/inetd.conf</filename> |
| 293 |
file.</para> |
177 |
file.</para> |
| 294 |
|
178 |
|
| 295 |
<para>When a modification is made to |
179 |
<para>Any modification to |
| 296 |
<filename>/etc/inetd.conf</filename>, |
180 |
<filename>/etc/inetd.conf</filename> will not take effect until |
| 297 |
<application>inetd</application> can be forced to re-read its |
181 |
<application>inetd</application> is forced to re-read the |
| 298 |
configuration file by sending a HangUP signal to the |
182 |
configuration file by using the following rc.d script:</para> |
| 299 |
<application>inetd</application> process as shown:</para> |
|
|
| 300 |
|
183 |
|
| 301 |
<example id="network-inetd-hangup"> |
184 |
<example id="network-inetd-hangup"> |
| 302 |
<title>Sending <application>inetd</application> a HangUP Signal</title> |
185 |
<title>Sending <application>inetd</application> a HangUP Signal</title> |
| 303 |
|
186 |
|
| 304 |
<screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen> |
187 |
<screen>&prompt.root; <userinput>/etc/rc.d/inetd reload</userinput></screen> |
| 305 |
</example> |
188 |
</example> |
| 306 |
|
189 |
|
| 307 |
<para>Each line of the configuration file specifies an |
190 |
<para>Each line of the configuration file specifies an |