In SUSE this can be done in Yast, I think this is a system function so it should be done through the distro's tools not KDE.

Why? Because Suse (and other some distros) has a tool for it?
This tool is not related with package management, and DE = Desktop Environment.

In any case, it is possible import Guidance's serviceconfig.py to KDE.

http://www.simonzone.com/software/guidance/

While I agree in principle that all settings should be managed from one place, like Windows and MacOS X, I don't like duplicating thing across KDE and a distro. SUSE has a program called Sax for managing displays, and so does KDE, so one should I use? Perhaps services (and other system settings) should be be able to be managed from KDE applications (where users would first check) but distro makers should also have the ability to easily replace them with their own tools.

	
I will try to extend my answer for better understanding.

The initial distributions were limited to packaging the programs, make its own package management system and to install certain programs by default (these three things should be the sole work of developers of any distribution).

These distributions were very difficult to use because the desktop environments lacked the necessary functions to make the system transparent to the user. Therefore, in order to provide to the user the easy configuration of their computer, new distributions were born, which put in its way the tools were missing to the desktop environments.

The desktop environments have evolved, and increasingly fewer tools are needed for each distribution, because are included in desktop environments, which is where they should be. In this way, the tools are standard, and are fully integrated with the environment, for a consistent desktop environment.

KDE already has a service manager for KDE-related services (run "kcmshell4 kcmkded")
However as every distribution can manager their services in a different way I don't know if this is possible.
IIRC Pardus done something similar for its distribution. (a KCM-like Service Manager)
Just my 2 cents.
Regards

*** Bug 183659 has been marked as a duplicate of this bug. ***

I was talking about something like this: http://kde-apps.org/content/show.php?content=114050
Consider to include it in KDE Admin, please.

The developer of that KCM will need to copy its source code to KDE playground then move to KDE Review, in order to move to KDE Admin,

Hey, I'm the writer of KDE Daemon Manager. Got an email telling me to come here. 

I'm perfectly happy for it to be part of KDE, that would be awesome - however I'm not sure how distro-centric the application is. It relies on daemons being inside /etc/init.d and chkconfig to perform the enabling/disabling. I'm not sure if this will cause a problem.

I've not tested on anything outside Kubuntu.  (I only got as far as releasing on kde-apps yesterday!)

Also it's still in an early development stage, the vision is to have it plugin-able, and have a small amount of service configuration inside the module.
It certainly needs to be better when it fails to start a service.

I'd appreciate testing feedback, and advice on where to improve. Along with guidance on getting it in core KDE (if applicable).

Once I've given it a tidy up and got some more comments from users saying it actually works I'll mirror a copy to playground.

@David: How is the module progressing at this time?

@Ben: In all honesty I've scarcely done anything, I took the time to sort out some other projects, and I've been swamped at work.

I'll try and get back on it over Christmas, and copy it to Playground so maybe other people can start testing and helping.

*** Bug 270004 has been marked as a duplicate of this bug. ***

It is sad that KDE distributions are reinventing the wheel over and over again, when the efforts to build a nice GUI could be shared, even if the underlying mechanism is distribution specific.

The kded KCM shows KDE services, and the systemd KCM shows all systemd services. Between the two, this is essentially done.