|KDED5(8)||kded5 User's Manual||KDED5(8)|
For sycoca, it monitors the directories containing .desktop files. When a file is added/removed, it waits 5 seconds (in case of a series of updates), and then launches kbuildsycoca5 to update the sycoca.
For KConfig, it checks newly-installed update files, i.e. the *.upd files used to update configuration files of users when the configuration file formats changes, and runs the KConfig update utility to perform the updates.
Those tasks are also run when kded5 is started to ensure that the user configuration is up to date.
You do not normally need to run kded5 directly; Plasma desktop sessions run it automatically, and it is started on demand when an application attempts to use a D-Bus interface provided by it or one of its modules.
Check the sycoca database, updating it if necessary, and exit.
Configuration file entries are read on-demand, so changes can be made while kded5 is running. However, all the current configuration options only really affect the startup behaviour of kded5.
The [General] section has the following options:
Whether to update sycoca at startup (default: true).
Whether to perform outstanding KConfig updates at startup (default: true).
Whether to check file timestamps when performing the initial sycoca update (default: true). See the documentation for kbuildsycoca5 for more details.
Whether to delay the initial sycoca update until about a minute after starting (default: false).
Each module also has a [Module-name] section in kded5rc, where name is the name of the module's desktop file without the .desktop extension. This contains an autoload option that specifies whether the module should be automatically loaded when kded5 is started (default: false). Note that this setting can also be changed via kded5's D-Bus interface.
Waldo Bastian <firstname.lastname@example.org>
- KDE's bugtracker
|2014-03-22||KDE Frameworks Frameworks 5.0|