Bug 283605

To be more specific, one way to achieve this is to do this - just before disabling strigi, read a config entry from share/config/nepomukstrigirc and dont do it if a certain value is present.

I think that's the intended behaviour already...?

This makes sense. The question is: where should we put the config option in the GUI? Should it be in the power management configuration as part of the profile? Or should it be in the Nepomuk KCM? The latter seems a bit forced to me.

As users wont really use that option (it only and almost always makes sense on tablets) I will suggest it as a non GUI option, that devs/packagers can use my putting inside global settings or something like that. And as its Nepomuk which does the disabling-indexing work, it should goto a nepomuk settings file.

I agree with Shantanu, I would not add an option for that. Depending on how Strigi is efficient and how much power it wastes (would be nice to have some data about this) we might even go as far as disabling this "sleep" feature in certain/all environments, or try to come up with better heuristics to define when/how to save power when on battery.

Hidden config in nepomukserverrc is just fine, IMO.

+1, but I would still be interested in how nepomuk affects power consumption in the average situation and if we can do something to improve that - I think it's quite a priority for Active as well.

+1 to config option in nepomukserverrc

Git commit daa5819b83823aa787205008f7d4b07132e6019d by Sebastian Trueg.
Committed on 12/10/2011 at 14:42.
Pushed by trueg into branch 'master'.

Added new hidden config option to disable suspend on powersave.

This is very useful on mobile devices basically always run on battery
and required for Plasma Active.
Packagers can just install a global "nepomukstrigirc" config file and
set "disable suspend on powersave" to "true".

BUG: 283605

M  +1    -0    services/fileindexer/eventmonitor.cpp
M  +5    -0    services/fileindexer/fileindexerconfig.cpp
M  +10   -0    services/fileindexer/fileindexerconfig.h

http://commits.kde.org/nepomuk-core/daa5819b83823aa787205008f7d4b07132e6019d

Git commit b12cda123b9adafe5e4fbcf655fdeff846f942d9 by Sebastian Trueg.
Committed on 12/10/2011 at 14:47.
Pushed by trueg into branch 'KDE/4.7'.

Added new hidden config option to disable suspend on powersave.

This is very useful on mobile devices basically always run on battery
and required for Plasma Active.
Packagers can just install a global "nepomukstrigirc" config file and
set "disable suspend on powersave" to "true".

BUG: 283605
FIXED-IN: 4.7.3

M  +1    -0    nepomuk/services/strigi/eventmonitor.cpp
M  +5    -0    nepomuk/services/strigi/strigiserviceconfig.cpp
M  +10   -0    nepomuk/services/strigi/strigiserviceconfig.h

http://commits.kde.org/kde-runtime/b12cda123b9adafe5e4fbcf655fdeff846f942d9

Git commit 3f274318965fe6f71cfecd7d557b06a0d08e88e3 by Sebastian Trueg.
Committed on 12/10/2011 at 14:44.
Pushed by trueg into branch 'master'.

Added new hidden config option to disable suspend on powersave.

This is very useful on mobile devices basically always run on battery
and required for Plasma Active.
Packagers can just install a global "nepomukstrigirc" config file and
set "disable suspend on powersave" to "true".

BUG: 283605
FIXED-IN: 4.7.3

M  +1    -0    nepomuk/services/fileindexer/eventmonitor.cpp
M  +5    -0    nepomuk/services/fileindexer/fileindexerconfig.cpp
M  +10   -0    nepomuk/services/fileindexer/fileindexerconfig.h

http://commits.kde.org/kde-runtime/3f274318965fe6f71cfecd7d557b06a0d08e88e3

That was quick :)

It took me a few times reading it, however, since there's a double negation:

Maybe renaming this option to 

indexOnPowerSave=

would prevent that? (Disable suspending == on, of course, but it's not that straight forward).

I've added the config file already to plasma-mobile/config/, but of course it's easy to change.

(In reply to comment #7)
> +1, but I would still be interested in how nepomuk affects power consumption in
> the average situation and if we can do something to improve that - I think it's
> quite a priority for Active as well.

I suppose the only problematic situation is the initial indexing on first
startup. In case of a new device this is a non-issue since there are no files.
But still, it would be interesting to do some tests in full indexing mode.

(In reply to comment #12)
> That was quick :)
> 
> It took me a few times reading it, however, since there's a double negation:
> 
> Maybe renaming this option to 
> 
> indexOnPowerSave=
> 
> would prevent that? (Disable suspending == on, of course, but it's not that
> straight forward).
> 
> I've added the config file already to plasma-mobile/config/, but of course it's
> easy to change.

Right, we could change it. I chose the "disable something" approach since the default is to not index. I thought that would be cleaner. But in the end I don't mind.

It's not a given that a new user does not have any files in her homedirectory. Quite likely even, we'll have some default content in Plasma Active.