Boy, what an old bug!
This has been discussed some times[1], but no conclusion reached. I'd like to
suggest (again, probably) the following:
Packages containing servers that can be started from inetd should all provide
an xinetd configuration file in /etc/xinetd.d. They will instantly work with
xinetd, and update-inetd can use the information, which is a superset
(right?) of that used by other inetd's, to update the old-school inetd.conf.
I think the situation is similar to the Debian menu .menu vs .desktop debate,
where the .desktop files contain a superset of the information in the .menu
files, so by providing the former, a package instantly works with OpenDesktop
environments, and update-menus/install-menu can use the data to support the
simpler window/desktop managers (the services are the applications that
provide menu entries, and the inetd variants are the window managers that
display the menu entries).
Jean-Christophe Dubacq suggested in the second thread below that a common
format be used to configuration data, from which the various configuration
files can be generated, but that thread seems to have died.
A legitimate question is whether the xinetd configuration format is a good
format. Are there, or will there be, even more "extended" inetd:s?
As a comparison, most packages on SUSE seem to provide xinetd configs, while
only three Debian packages do so.
[1] For example
http://lists.debian.org/debian-devel/2006/02/msg00446.html
http://lists.debian.org/debian-devel/2006/08/msg01265.html
--
Magnus Holmgren holmgren@lysator.liu.se
(No Cc of list mail needed, thanks)
Attachment:
pgpOJwHduTj4d.pgp
Description: PGP signature