2014-07-23 12:07 GMT+04:00 Vadim Zhukov <[email protected]>: > 2014-07-23 4:24 GMT+04:00 Amit Kulkarni <[email protected]>: >> On Tue, Jul 22, 2014 at 2:26 PM, Vadim Zhukov <[email protected]> wrote: >>> >>> CVSROOT: /cvs >>> Module name: www >>> Changes by: [email protected] 2014/07/22 13:26:46 >>> >>> Modified files: >>> faq : current.html >>> >>> Log message: >>> Notify KDE4 users about increased file descriptors pressure. >>> >> >> wow! Is there a way to turn this off @ runtime or compile time? if not >> changed, any terrible side-effects? thanks for your efforts! > > You can tweak the the "PreferredMethod" in "[DirWatch]" section in > default application configuration file > ($KDEHOME/share/apps/config/APPNAMErc). Yes, this could and should be > tweaked per application. Possible values: > > Fam > Stat > QFSWatch (previous value, effectively same as "Stat") > INotify (current default) > > Note that then you'll get constant CPU and disk eating. Which is > especially noticeable for laptop users.
Just realized that I was blind and thus wrong. You CAN edit global setting for KDirWatch (which could be overriden on per-app basis) using the following command: kwriteconfig4 --group DirWatch --key PreferredMethod METHODNAME where METHODNAME could be set to one of the following (case-sensitive): Fam QFSWatch Stat any other value imposes usage of inotify. For per-app change, add the "--file /path/to/app-rc-file/that/usually/lives/under/KDEHOME/e.g./home/joe/.kde" arguments before METHODNAME (without quotes, of course). You can see what method is actually used by enabling KDirWatch debugging in kdebugdialog4, starting application from the terminal emulator and looking at the application output.
