On Thursday, 29. November 2001 00:18 Wilco Greven wrote: > It might be kded.
Yes! Thanks for that hint, kded seems to be the disk-access trigger. The basic situation is unchanged: when I start any Kde application (let's say konsole) it starts also kded. When I kill kded the disk access stops. Surprisingly I can continue working without kded running, but I don't feel good doing so. I have disabled all installed kded modules by moving them away from $KDEDIR/share/services/kded/ without success. >From README.kded: |Example kdedrc file with default values: |[General] |PollInterval=500 |NFSPollInterval=5000 |HostnamePollInterval=5000 |CheckSycoca=true |CheckUpdates=true |CheckHostname=true I have modified all of these values in my ~/.kderc (that should be my local incarnation of kderc. Correct?) and manually started kbuildsycoca after editing, but the changes have *no* effect. Additionally I have stopped the automounter and the NFS-related daemons. No change. One piece of new information: When I start kbuildsycoca of konsole from a command line I get an error message: |[EMAIL PROTECTED]:~$ kbuildsycoca |Warning: kbuildsycoca is unable to register with DCOP. |Property 'Export' is defined multiple times (KOfficeFilterDialog) |Property 'Import' is defined multiple times (KOfficeFilterDialog) What can this tell me? Following the idea that the above messages have something to do with koffice I did apt-get remove koffice. No change. -- Udo Burghardt
