Contents
Summary
Systemd includes various features to allow socket activation in a similar style to xinetd. Rather than requiring a separate package which needs to be configured and enabled, all packages that require xinetd should be updated to instead use systemd socket activation.
Owner
- Name: Colin Guthrie
- Email: colin@mageia.org
Resources
All maintainers of packages that require xinetd for activation.
Current status
- Targeted release: Mageia 4
- Last updated: 2013-01-21
- Percentage of completion: 0%
Detailed Description
Any package which leverages xinetd for on-demand activation should be ported to use systemd socket activation instead
While xinetd should still be shipped and supported, there is no need to rely on a separate application when the required functionality is available in the core OS.
Why it would be good for Mageia to include it
It keeps the activation functionality performed by one system for all services, thus making the system simpler to understand and less confusing for new system administrators. It also ensures a very clear environment for launching each service and allows more advanced features regarding resource management and control to be more fine grained (i.e. each launched service will have it's own cgroup, not just inherit the cgroup from xinetd)
Test case
Each package needs to be tested to make sure it works.
Software / Packages Dependencies
None, all the functionality is built in.
What could disrupt development of this new feature
Not much.
Planning
None needed.
Contingency
xinetd will still be shipped and supported for those that need it/have working setups. If we do not complete this task then no real harm done.
