On 2007-02-10 02:02:46 +0200 Philippe Roussel <[EMAIL PROTECTED]> wrote:
Hi all
I've just built GNUstep and applications from svn (revision 24494) and now
GWorkspace starts mdextractor if it isn't already.
This happens only if indexing is enabled. To enable/disable indexing you must use
SystemPreferences and select the "Indexing" module; here you can select the
paths that you want to be included or excluded by mdextractor and if it must be started
by GWorkspace.
The problem is that
mdextrator seems to be a cpu and memory hog :
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME COMMAND
30304 philou 25 0 172m 22m 7876 R 86.8 1.5 6:13 mdextractor
Is this normal, should I wait longer for mdextractor to finish its work ?
The first time you run mdextractor it needs to create its database; this means
that it must extract the contents of all the indexable directories (default
your home directory and the GNUstep Applications, Headers and Docomentation
directories). This can take some time...
When the database is created, all the successive work of keeping it updated is
not cpu intensive.
And on a close enough topic : will MDFinder.app replace GWorkspace actual
search tool ?
Perhaps, in the future; for the moment it is a new thing that, besides a good
name for all the stuff and some icons, needs to be used and tested by the
GWorkspace users.
Thanks,
Philippe
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
