> I have now a problem. Apparently, tracker-extract fail on some files, > and I find it very difficult to get log information about the errors. > let me describe the program flow: > > - first, tracker-control starts tracker-miner-fs > - then, tracker-miner-fs browse the directories and ask > tracker-extract (via dBus) to index some files > - tracker-extract is started, overwriting the old tracker-extract.log file > > now: > > - tracker-extract fail on some file, it stops > - tracker-miner-fs skips this file (I suppose) and continue on to the next > file > - on the next file, tracker-miner-fs calls tracker-extract > - tracker-extract starts and overwrite the tracker-extract.log file > containing precious information about the error > > is it possible to have a configuration option for all tracker > executables that would append to the existing log file instead of > overwriting it? >
There is no such option, but may be useful in the case of tracker-extract. Anyway, for debugging errors on specific files with tracker-extract you can always manually call it like: $> /usr/libexec/tracker-extract -f /path/to/file/with/problems (the path of tracker-extract may be different in your system) This is usually enough for debugging such errors. Cheers, -- Aleksander _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
