On Tue, Nov 11, 2008 at 12:51 PM, Martyn Russell <[EMAIL PROTECTED]> wrote: > Chris Fanning wrote: >> On Tue, Nov 11, 2008 at 12:30 PM, Martyn Russell <[EMAIL PROTECTED]> wrote: >>> Chris Fanning wrote: >>>> On Tue, Nov 11, 2008 at 10:24 AM, Martyn Russell <[EMAIL PROTECTED]> wrote: >>>>> Chris Fanning wrote: >>>>>> Hi, >>>>> Hi :) >>>> Ok, I tried it and it works. Users are going to love this! >>>> >>>> I think it would be nice to be able to pass a different >>>> /path/to/my/index_server/tracker.cfg to trackerd on the index_server, >>>> or equally be able to do the same when starting trackerd on the node, >>>> but I hacen't seen an option for this in the manpages. >>> I suppose you could ln -s the file for now. We could add an option to >>> load the config from somewhere else actually. Should be really quick to do. >>> >>>> One small problem. >>>> I start trackerd on the index_server. And when I start >>>> "/usr/bin/trackerd --no-indexing" on the node it reports "WARNING **: >>>> Tracker daemon is already running - exiting" >> >>> Just out of interest, why run another instance of trackerd? >>> >> One is running on the index_server: >> su - uid >> dbus-launch trackerd > > The daemon should start itself, is there actually another process > already started at this point? after entering via 'su - username', the only processes running under 'username' are 1. su 2. bash trackerd does not start dbus by itself, that's why I use "dbus-launch trackerd"
> >> And another is running on the desktop_server (invoked when user starts >> tracker-search-tool). >> >>> Yea, this tries to get the DBus name when it starts and it if is already >>> occupied then it exits assuming it is already running. You can get >>> around this by using different DBus session buses. >>> >> ok. escuse my ignorance but, as I'm running these instances on two >> different boxes (trackerd and dbus), aren't I already using different >> DBus session buses? > > Ah, that's TRUE. Note. If you call the Tracker DBus API, it should start > it for you. I would advise not starting it yourself, Maybe trackerd is finding a PID file or lockfile someplace? If both trackerd on index_server and desktop_server are reading the same file that might explain it. > and just using the > config option to disable indexing instead. The reason I asked about passing a different config to trackerd was because of this. Both the desktop_server and the index_server share the same /home. That means trackerd reads the same config. At the moment (to get arounf this) if wrapped trackerd on the node with /usr/bin/trackerd #!/bin/bash /usr/bin/trackerd.orig --no-indexing Cheers, Chris. > > -- > Regards, > Martyn > _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
