On Monday 10 July 2006 18:48, Joachim Schrod said:
I don't use the KDE desktop, but I use KDE applications from time to time. (I use an fvwm-based desktop.) When I start the first one, background daemons get started; I assume for application communication and such. They get shot down with the last KDE application terminating.
Start of these additional programs increases application startup time, or don't they? I would like to start them in advance, when I start my X session. Is there a list of daemons that should/could be started? Or do I need to analyse the KDE startup scheme myself?
Yes, it's starting kded (inetd-like, frequently used kde miniservices like file change notification, network status monitoring, media hotplug), dcopserver (IPC) and kdeinit (base process that speeds kde programs' library loading by loading the new prog as a library and forking) - they all takes some time when repeated for each and every process. The easy way: Start a useful kde background program like klipper (persistent clipboard history) at session startup. It will start the daemons then, and keep them running for other apps to use The hard way: Read through /opt/kde3/bin/startkde and figure out which bits you want to start, and which (kdesktop, kicker, kwin) you don't need under fvwm. Someone (see below :)) should take care of the hard way soon, I see a lot of demand for KDE apps from people who don't want the whole desktop. HTH WIll -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com