> Could you add support for systemd and xinetd in inetutils? > I've attached working configs (systemd service and socket > files and xinetd config). > > What does that mean exactly? I think those files are better > distributed by your operating system vendor than having them be > part of inetutils.
Since many distributions now use systemd as init system, many projects now provides the systemd files to enable/start/etc their daemons. This remove duplicate works for the distibution maintainers and the upstream developpers are better suited to handle these files as they know the best way to operate their daemon. I'm inclined to think that this should be done by the distribution maintainer. Not all systems use systemd, some use System V init in various forms, some use a BSD like init system. The files are also so tiny that it isn't that much work to create them -- I think most distributions wouldn't even install them. How about a chapter in the documentation about setting up daemons? Does anyone else have a strong opinion about this? Supporting systemd would mean adding these file to the source tarball and installing them in /usr/lib/systemd/system (default location). They would need to be generated, since daemons (in.ftpd, etc) are normally installed in PREFIX/libexec. And it cannot be done by default, since we run on many platforms.
