Hi, Jamie, Jerry, Halton and I discussed this several times last weeks. Here are some suggestions.
1. Shared NFS home directory issue. In this case, 2+ machines runs tracker with same DB and conflicts. A resolve is tracker use separate preference/DB directory. Such as: ~/.tracker/machine-uuid-34738-34873/trackerDB 2. Don't index remote mounted directories by default. We could also add an option for this. User could choose whether to index remote file systems by default. This could not resolve all of course but it could work around many conflict and performance issues. -rick jamie wrote: >> On Fri, 2007-10-12 at 21:28 +0800, Jerry Tan wrote: >> >> >>> I have two PC, both have its own OS, >>> but one account share the same home directory by nfs share. >>> >>> I can run trackerd on one PC, >>> >>> but can not start trackerd on another PC, because there is a lock. >>> >>> >>> How can I use tracker on this PC? >>> >>> >>> >>> >> you risk corruption if NFS file locking is broken which is why we >> disabled it >> >> we had an option to move lock file to /tmp rather than $Home to allow >> multiple sessions from a central NFS home dir to be run - I will >> reenable it I suppose shortly >> >> >> _______________________________________________ >> tracker-list mailing list >> [email protected] >> http://mail.gnome.org/mailman/listinfo/tracker-list >> >> > How about this? > > when the first trackerd runs from one PC, it own the lock. > > if one guy wants to start trackerd from another PC, tracker found the > lock is there, > then it will start with noindex option, it can still handle user request, > then tracker-search-tool can work on it also. > _______________________________________________ > tracker-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/tracker-list > _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
