#41 Services which may autostart
Closed: Invalid None Opened 9 years ago by toshio.

http://lists.fedoraproject.org/pipermail/devel/2010-December/146750.html

  • exception for ssh -- justification: if you're installing remotely, you need this in order to login after reboot.
  • Dbus and default syslog variant are examples of "things needed to run a desktop session" or something.
  • iptables, auditd, restorecond are examples of things that add to system security in a default install. For this category we'd want to be careful, do we also want to allow fail2ban or denyhosts to run by default if they're installed?
  • readahead -- system optimization
  • tons of unit files that lennart has done as part of the switch from monolithic initscripts -- can we differentiate between a service and other types of units?

Replying to [ticket:41 toshio]:

  • Dbus and default syslog variant are examples of "things needed to run a desktop session" or something.

I'd argue that syslog is also an example of "thing to run on a server", not just desktop.

<nod> (to things to run a server). Do we need a separate category for that, though? Maybe it would be -- "things that are needed for any Linux system". and "things that are needed for a modern desktop system".

Also note: dwalsh stated that restorecond is not needed and currently defaults to off so we should take that off the list.

Lennart proposed that we permit non-network services which do not require any configuration to be enabled by default, and also allow specific exceptions such as:

  • dbus
  • openssh
  • iptables
  • auditd
  • udev
  • readahead
  • syslogd
  • NetworkManager
  • abrtd

List of packages which contain services which currently autostart:

abrt
acpid
at
audit
autofs
avahi
bluez
cluster-glue
cobbler
coda-client
cpuspeed
cronie
ctrlproxy
dbus
dkms
exim
fence-virtd
firebird-superserver
firstboot
fnfx
freenx-server
gadget
gpm
gvrpcd
hal
hsqldb
ifplugd
ipmiutil
iptables
iptables-ipv6
irqbalance
iscsi-initiator-utils
isdn4k-utils
koji-builder
libvirt
libvirt-client
lvm2
mdadm
nfs-utils
ocfs2-tools
olpc-utils
openct
openslp-server
openssh-server
pcsc-lite
pop-before-smtp
portreserve
preload
qemu-common
qemu-user
quagga
rhnsd
rpcbind
rp-pppoe
rsyslog
sblim-gather
sendmail
snort
spice-vdagent
sysklogd
sysstat
udev
wine-desktop
xen
xen-runtime
xinetd
yum-updatesd

FESCo generated a list and exceptions, which I have added to the wiki here:

https://fedoraproject.org/wiki/User:Kevin/DefaultServices

See also: https://fedorahosted.org/fesco/ticket/544

FESCo would like the FPC to review this and tell us if they don't like any parts of it or would like us to handle exceptions moving forward.

Replying to [comment:5 kevin]:

FESCo generated a list and exceptions, which I have added to the wiki here:

https://fedoraproject.org/wiki/User:Kevin/DefaultServices

See also: https://fedorahosted.org/fesco/ticket/544

FESCo would like the FPC to review this and tell us if they don't like
any parts of it or would like us to handle exceptions moving forward.

If ifplugd is enabled by default then what happens if NetworkManager
is installed, too? Same thing with rsyslog and sysklogd.

xinetd provides some simple unix services on its own, should they be
enabled by default as well? I'm think not.

I'm not convinced about ifplugd, isdn4k-utils and rp-pppoe. I think
they require some configuration to run properly. Moreover, rp-pppoe
actually starts a server, while it can be used for client-only
connections, too (and I think it usually is).

Login to comment on this ticket.

Metadata