Starting services by default

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Steal from Spot)
 
(change exceptions to be from FESCo)
Line 22: Line 22:
 
* xinetd
 
* xinetd
  
All other services must not be enabled by default. If you think that your package contains a service that should be enabled by default, but does not meet the above criteria, you may request an exception from the Fedora Packaging Committee.
+
All other services must not be enabled by default. If you think that your package contains a service that should be enabled by default, but does not meet the above criteria, you may request an exception from the FESCo.

Revision as of 17:58, 23 February 2011

Services which may be enabled by Default

If a service does not require configuration to be functional and is not network enabled, it may be enabled by default (but is not required to do so).

In addition, any service which does not remain persistent on the system (aka, it "runs once then goes away") and does not require configuration to be functional may be enabled by default (but is not required to do so). Examples of "runs once then goes away" services include iptables and udev.

Finally, there are some services which are permitted to be enabled by default as specific exceptions:

  • autofs
  • avahi
  • coda-client
  • ifplugd
  • iscsi-initiator-utils
  • isdn4k-utils
  • nfs-utils
  • ocfs2-tools
  • openssh-server
  • rpcbind
  • rp-pppoe
  • rsyslog
  • sysklogd
  • xinetd

All other services must not be enabled by default. If you think that your package contains a service that should be enabled by default, but does not meet the above criteria, you may request an exception from the FESCo.