Services which may be enabled by default
Only services that meet the criteria below are permitted to be enabled by default on package installation.
For the purposes of this document, a "service" is defined as one or more of:
- A daemon or process started using a systemd service unit.
- A daemon or process that is invoked by socket activation, either by using a systemd socket unit, D-BUS activation or similar behavior.
- A systemd timer unit that runs periodically.
Installation of the package providing the unit auto-started by this preset may not change the behavior of any other service running (or potentially running) on the system.
Services must not in the course of normal operation fail to start in such a way that the system state is anything other than "running".
Services which only function if certain hardware is present, or may fail if certain hardware is not present, must either be hardware activated or must start conditionally. Conditional starting may be accomplished by utilizing the conditional functionality of systemd. If the capability to inquire about the specific condition does not currently exist, you must request it be created and provide the necessary criteria. If it is not possible to create a specific conditional systemd validation, you may request an exception to this restriction until such time the conditional functionality can be created.
Locally running services
If a service does not require manual configuration to be functional and does not listen on a network socket for connections originating on a separate physical or virtual machine, it may be enabled by default (but is not required to do so).
Example: Local D-BUS services
In addition, any service which does not remain persistent on the system (aka, it "runs once then goes away"), does not listen to incoming connections during initialization, and does not require configuration to be functional may be enabled by default (but is not required to do so).
Some services which are permitted to be enabled by default as specific exceptions. Services that should be enabled by default throughout all of Fedora must be approved by FESCo. Services that should be enabled or disabled by default only on one or more of the Fedora Editions must be approved by those Editions' Working Groups.
- FESCo approves openssh-server to run by default on Fedora in general.
- Workstation WG approves openssh-server to be disabled by default on the Workstation Edition.
Current list of enabled/disabled services
How to enable a service by default
Unit files must correspond to the Fedora Packaging Guidelines. Services are enabled or disabled by default through systemd preset files. Preset files can be overridden by a local administrator, but a set of defaults are provided by Fedora.
If the service should be enabled by default, it must be added to one of the distribution presets files (see above).
For services which meet one of the conditions listed above, a ticket should be filed in bugzilla. If the preset should be changed for versions other than rawhide, indicate that in the ticket.