A short time after booting I get this message:

"Suspending the indexing of files to preserve resources."

From then on the Strigi Search Service shows as suspended.

Is this normal or does it mean there is a problem?

Can it be un-suspended?

It is normal - if you are doing something CPU intensive, strigi will get suspended not to be in the way of more important processes.

To resume it just right-click the nepmuk icon in the tray and choose the appropriate option.

Thanks, I assume this is only an issue when you first start using Strigi as it has to index the whole disk.

ivan wrote:It is normal - if you are doing something CPU intensive, strigi will get suspended not to be in the way of more important processes.

To resume it just right-click the nepmuk icon in the tray and choose the appropriate option.

Ivan, I've noticed this seems to only happen when using Lancelot to start an application using the search option.

Selecting an application from the menu, from krunner or using the kickoff search does not cause this problem on my system.

I've noticed that. Have no idea why Strigi detects a 'high usage' when you start searching. It may have something to do with the enabled runners (runners in kickoff are on a bare minimum) or something.