Useful daemons

Hi

This question has been posted a lot of times but I cannot find an exhaustive answer, particularly for openSuse 11.3 .

So, these are daemons running on our server (Intel x86_64):

SuSEfirewall2_init on
SuSEfirewall2_setup on
acpid on
apache2 on
auditd on
cron on
dbus on
earlysyslog on
fbset on
haldaemon on
irq_balancer on
kbd on
mcelog on
mysql on
network on
network-remotefs on
nscd on
ntp on
postfix on
random on
rcl on
rpcbind on
smartd on
splash on
splash_early on
sshd on
syslog on
tomcat6 on
xdm on

Which ones are useful ?

We need Apache2, tomcat6, mysql and ntp.
We use suse firewall, access the server remotely via SSH and do not mount any external / remote filesystem.

So, basically I would like to remove useless daemons.
network-remotefs seems to be one of these but can’t be stopped.

Thanks

On 2011-01-05 14:06, josiasseb wrote:

> Which ones are useful ?

All.

> network-remotefs seems to be one of these but can’t be stopped.

Obviously >:-)


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Some of the daemons are there to provide system services and are not explicitly contacted by the end user. AFAICT all in your list are needed.

People get worked up about service daemons, thinking they eat up a lot of RAM. Actually most of them have small footprints. It’s things like a desktop and web browser that chew up RAM. Also Java app engines.

I thought that network-remotefs was useful only to mount remote filesystem.
And that rpcbind was not used by sshd by example.

Am I wrong ?

On 2011-01-05 15:36, josiasseb wrote:
>
> I thought that network-remotefs was useful only to mount remote
> filesystem.

If you look the source, you will notice that what it does is start another
service with a different parameter. If there is nothing using remote
filesystems this way, the service does in fact not run, and thus, can’t be
stopped, there is nothing to stop.

> And that rpcbind was not used by sshd by example.

No, it is used by nfs.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I assume your question really is based on a desire to decrease attack surface by shutting down unnecessary services.

Instead of inspecting each and every daemon, I’d recommend you instead consider applying either AppArmor or SELinux policies which are pre-configured templates created to achieve your goal. As to whether you choose AppArmor or SELinux, you’ll have to make your own decision, both are different approaches to achieve the same goal.

Tony

Thanks for all these advices.