[synopsis]
\fIreconf-inetd\fR \fI[\-\-verbose]\fR
.br
\fIreconf-inetd\fR \fI\-\-sanity-check=fragment [... fragment]\fR

[description]
reconf\-inetd is a maintainer tool that updates inetd.conf. Such updates are
based on xinetd.conf-like configuration fragments in /usr/share/reconf-inetd
(where server packages install their fragments) and /usr/lib/reconf\-inetd
(where reconf-inetd keeps track of which inetd.conf entries have been added by
itself).

reconf\-inetd identifies every inetd.conf entry based on the combination of
three fields: service name, protocol, and server path. This allows multiple
inetd.conf entries for the same service, eg. for IPv4 and IPv6 versions, as
well as for different upstreams (eg. proftpd versus ftpd\-ssl).

reconf\-inetd will not add inetd.conf entries for services whose server path is
non\-existent, or whose combination of protocol, service name and server path
matches an existing inetd.conf entry.

reconf\-inetd does not support internal services.

[xfragment files]

According to xinetd.conf(5), xinetd fragments must have the following fields:

  socket_type       (mandatory)
  wait              (mandatory)
  user              (non\-internal services only)
  server            (non\-internal services only)
  protocol          (RPC and unlisted services only)
  port              (unlisted non\-RPC services only)

If the protocol field is omitted and the service is listed, reconf\-inetd will
assume the protocol of the first matching entry from /etc/services. That will
be tcp or udp, which currently implies IPv4, so if the intention is IPv6, then
tcp6 or udp6 should be explicitly specified in the protocol field.

Unlike, regular xinetd fragment files, reconf\-inetd fragment files must have
only one service per file. If your package provides more than one service,
please install a separate fragment file for each service. This is the case to
allow for removal of individual services, by simply removing the related file.

/usr/share/reconf\-inetd fragments are not configuration files; they're just
input to reconf\-inetd. Local admin configuration should be applied to
inetd.conf

[files]
reconf\-inetd declares a file\-based dpkg trigger on /usr/share/reconf\-inetd.
Shadow fragment files are stored in /var/lib/reconf\-inetd.

A log file is kept at /var/log/reconf\-inetd.log

[bugs]
Known issues and missing features are listed in
/usr/share/doc/reconf\-inetd/TODO

[history]
reconf\-inetd is a replacement for update\-inetd. The motivation for and design
of reconf\-inetd is detailed at the Debian Enhacement Proposal 9, at
http://dep.debian.net/deps/dep9/, a copy of which is locally available at
/usr/share/doc/reconf-inetd/dep9.html

[author]
\fBreconf\-inetd\fR was designed, documented and implemented by Serafeim
Zanikolas <sez@debian.org>

[see also]
inetd.conf(5), xinetd.conf(5), inetd(8), update\-inetd(8), deb-triggers(5)

