Hi! Am 16.05.2014 um 18:18 schrieb Ralph Böhme <r...@netafp.com>: > >> With this in mind, it's quite bad that we don't have some sort of watchdog >> or way to keep it up and running. We could easily do this in >> tracker-miner-fs. Part of me thinks we should actually have a >> tracker-control --daemon which watches all process and keeps some sort of >> journal / log going and also maintains processes like tracker-extract keep >> running. I should add, this is something that nearly EVERY embedded solution >> does itself with some script which keeps miner-fs running (not even >> tracker-extract), because there is no other way to guarantee Tracker is >> there to catch all events. > > Ok, thanks. So taking up on this approach I wrote two Solaris SMF service > manifests (resembles systemd) for tracker-miner-fs and tracker-extract. This > works in that it restarts crashing tracker-extract and then tracker-extract > continues indexing. > > Unfortunately this doesn't work for files that crash it reproducibly as you > mention below: > >> The only downsides I see are repeated attempts causing a circular problem >> with tracker-extract. > > Definitely. For uses with possibly many files causing crashes this renders > Tracker useless.
Example: http://pastebin.com/XrTBuLky A single PDF that causes tracker-extract to crash in libpoppler again and again. I'm running tracker-extract and tracker-miner-fs via Solaris SMF (think systemd) and that keeps restarting tracker-extract which keeps crashing. :( -Ralph _______________________________________________ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
