Hi, Darren let me to make it clear. When community release tracker 0.6.6 tarball, it is enabled by default in gnome-session, that means when gnome-session start, trackerd will be started also.
When I make the pkg on solaris and integrate it into our internal gnome build for test, I disable tracker autostart in gnome-session. that's why Robert kinsella found that he needs to start it manually. The reason why I disable it for our internal build is that: Because trackerd will index user' home directory by default, If one user's home directory is huge, indexing for the first time may be time-consuming. And out internal gnome build need to be deployed to one internal Sunray Server, which is main desktop for staff in my team also. I don't want to bother anyone who are not interested in tracker in our internal sunray server that's why I disable it temporally in the internal build. Darren J Moffat wrote: > Jerry Tan wrote: >> Darren J Moffat wrote: >>> Robert Kinsella wrote: >>>> Hi Darren, >>>> I started trackerd manually in all zones, gnome-session (testing >>>> on gnome2.22) did not start the daemon automatically. >>> >>> Is this is bug that will be fixed before integration or an >>> architectural issue that it can't start up by default ? >> It is not a bug. >> because when I build the package with internal gnome build, >> I disable trackerd autostart within gnome-session. > > So the default in the trackerd/gnome-session source is for it to be > enabled ? Why are you changing the upstream default ? > > I'm not personally that bothered wither it is on or off by default but > the above seems to imply that this case is proposing something > different from the upstream default and I believe that needs to be > justified. > >> so only interested user will get to use it. > > Then I'm confused by the statement in the original proposal: > > " Tracker daemon will be started with gnome-session. > User can run gnome-session-properties to enable/disable it." > > That implies to me that the default is enabled not disabled. >
