Hi, Darren, please see my answer below.
>
> What about the question where the user is logged in multiple times
> from different systems all sharing the same home directory ? Will there
> be only one copy of trackerd ? or will there be multiple copes
> possibly corrupting the database as they all try to write to it ?
>
> You also haven't answered if the database works cross architecture.
>
1. Tracker daemon has thinking about this problem when design.
so when tracker is started, it will check one lock file under Home
directory.
If it can lock it, tracker daemon will be started normally.
If it find that file is locked by others, tracker daemon will start
in read-only mode,
which means that it can still handle user request for search, but can
not write indexing data into database.
By this, it can avoid corruption for database.
2. Tracker depends on SQLite API to read/write indexing data.
I have tested that SQLite works cross architecture.
I create some data using SQLite on Solaris X86, and share the
database file,
Then I login to another Solaris SPARC to mount that directory, and
I found I can read the data using sqlite.
So there is not problem for this issue.
>> >
>> > * How does this work with Trusted Extensions ? for example will
>> there
>> > be a trackerd running per label ?
>>
>> I don't think that there is any difference when run with Trusted
>> Extension.
>> Please correct me if I am wrong.
>
> Trusted Extensions have multiple gnome desktops each running in a
> different zone (eg multiple copies of nautilus) including some stuff
> for the user running in the global zone (eg metacity).
>
> This case needs to document wither or not tracker will be running in:
> a) the global zone (Trusted Path)
> In which case it *will* need to be label aware and not
> use a single database.
> b) all zones that represent lables.
> c) not run at all with TX enabled (not ideal)
>
Tracker starts in one gnome environment,
In Trusted Solaris, each Zone has its own gnome environment,
So I don't think there is any problem running tracker.
