Starting services by default

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(change exceptions to be from FESCo)
(Services which may be enabled by Default)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Services which may be enabled by Default ==
 
== 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).
+
If a service does not require configuration to be functional and does not listen on a network socket, 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.   
+
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). 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:
 
Finally, there are some services which are permitted to be enabled by default as specific exceptions:
Line 10: Line 10:
 
* avahi  
 
* avahi  
 
* coda-client  
 
* coda-client  
 +
* dbus
 +
* firewalld
 
* ifplugd  
 
* ifplugd  
 
* iscsi-initiator-utils  
 
* iscsi-initiator-utils  
 
* isdn4k-utils  
 
* isdn4k-utils  
 
* nfs-utils  
 
* nfs-utils  
 +
* NetworkManager
 
* ocfs2-tools  
 
* ocfs2-tools  
 
* openssh-server  
 
* openssh-server  

Latest revision as of 19:08, 5 September 2012

[edit] Services which may be enabled by Default

If a service does not require configuration to be functional and does not listen on a network socket, 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"), 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). 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
  • dbus
  • firewalld
  • ifplugd
  • iscsi-initiator-utils
  • isdn4k-utils
  • nfs-utils
  • NetworkManager
  • 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.