I take your point, but KDE ksysguard daemon (ksysguardd) is in /etc/init.d though…
Not switched on here, though I admit I do not know if this was by default from the install.
Of course after install I walked through all services in YaST > System > Systemservices (Runlevel) to check if they are needed. Primary for not having not needed services listening at IP ports (I rather check this instead of running the firewall, but you could do both).
I couldn’t find a page on the wiki describing the System Services.
What is the difference between the YaST module and the Service Manager in the System Settings?
Is there a documented list of defaults anywhere that I can compare my current system to?
I any case the YaST mudule is about the system and has basicaly nothing to do with the desktops that are going to run GUI login.
What you call “Service Manager in the System Settings” I think is from the KDE System settings (I have a dutch translation here and guess what the original text was) > Adcnced > KDE system services. As it says, it is basicaly about KDE, not about the system.
I admit that the KDE developers, developing for many Operating Systems (including Windows) do not develop with YaST in mind. Thus they tend now and then to create management tools for the system, just to make things easier for the KDE user. You will recognize this because when you want to configure there the root password is needed.
I think part of the part of the confusion here is due to the fact that you do not have a clear view on how an operating system like Linux is build. It is a multi user system. That means that there is a clear dividing line between the system and the user sessions.
. boots end shuts down;
. has services running (the starting and stopping of these is generaly seen as part of the boot and shutdown sequences);
. is managed by root;
. all this without any user login in!
The user sessions:
. start with a login (in a terminal/console CLI or in the GUI);
. ends with a logout;
. can have many enviroinments like different shells for the CLI and different desktops for the GUI;
. there can be several sessions running at the same time, started by different users, and having different of those environments.
When you understand the idea behind this, you will understand that a KDE configuration is done by user x for his usage of KDE and has no influence on another user using KDE, let alone another users using Gnome at the same time or at different times.
Thus when you want to speed things in general, you must look as the different components:
. The boot/shutdown sequence (I allways wonder why people complain about boot times. one also has to wait for a proper shutdown or not?). Here knowledge about the system and the power of root is needed. Now it may be that apart from being an end-user on the system you (as humann being) also are the System Manager (root). But allways keep in mind that these are two different roles that should not be mixed. Typing the root password changes your role!
. The login process of a particular (or several) users. Looking at this could go (for a GUI) into deciding if you realy need all those desktop effects. Also when you have the restore desktop function on, the startup could involve the start of many applications (that were left running on logout). Ask yourself if it is honest to add the start of Amarok, three FF windows, Skype and half a dozen others to the login time.
Hope the above helps in getting more iinsight in the wonderfull world of Unix/Linux.