: How can I hack the existing script to support multiple rsync module
you might want to just consult some rsyncd resources to answer this
question, i believe adding a new "[modname]" block is how you add a
module, with the path/comment keys listed underneight, however...
1) i don't believe it'
nable command is simple enough, but the rsyncd-start
>> command
>> >> takes a -d (data dir) as an argument... Since I'm hosting 4 different
>> >> instances, all with their own data dirs, how do I do this?
>> >>
>> >> Also, you have to specif
You can either use a dedicated rsync port for each instance or hack the
existing scripts to support multiple rsync modules. Both ways should work.
Bill
On Tue, Jul 1, 2008 at 3:49 AM, Jacob Singh <[EMAIL PROTECTED]> wrote:
> Hi Bill and Others:
>
>
> Bill Au wrote:
> > The rsyncd-start scripts
Hi Bill and Others:
Bill Au wrote:
> The rsyncd-start scripts gets the data_dir path from the command line and
> create a rsyncd.conf on the fly exporting the path as the rsync module named
> "solr". The salves need the data_dir path on the master to look for the
> latest snapshot. But the rsyn
The rsyncd-start scripts gets the data_dir path from the command line and
create a rsyncd.conf on the fly exporting the path as the rsync module named
"solr". The salves need the data_dir path on the master to look for the
latest snapshot. But the rsync command used by the slaves relies on the
rs
Hey folks,
I'm messing around with running multiple indexes on the same server
using Jetty contexts. I've got the running groovy thanks to the
tutorial on the wiki, however I'm a little confused how the collection
distribution stuff will work for replication.
The rsyncd-enable command is simple
