Thank you, it works now!!<br><br><div class="gmail_quote">On Tue, Jan 12, 2010 at 21:00, Zooko Wilcox-O'Hearn <span dir="ltr"><<a href="mailto:zooko@zooko.com">zooko@zooko.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tuesday, 2010-01-12, at 10:48 , Wassim Drira wrote:<br>
<br>
> We use Xen Server to host multiple storage servers. We copied the<br>
> client multiple times to use it. The problem that many clients are<br>
> seen as a unique by the introducer. After few investigation, I<br>
> remark that multiple clients have the same "peerid" (I choose<br>
> different "nickname" for each client).<br>
><br>
> Did you have an idea how to make the PeerID different?<br>
<br>
</div>The peerid is generated by the "tahoe create-client" command (which<br>
is, confusingly, also the command to create a server). The nodeid is<br>
stored in "private/storage.furl" and in "my_nodeid". See docs/<br>
configuration.txt for details about those files: <a href="http://allmydata.org/" target="_blank">http://allmydata.org/</a><br>
trac/tahoe/browser/docs/configuration.txt .<br>
<br>
So the easiest solution is that if you want to create a second<br>
client, run the "tahoe create-client" command a second time and it<br>
will generate a new nodeid. Don't copy an existing .tahoe directory<br>
as a way to create a second client.<br>
<br>
Regards,<br>
<br>
Zooko<br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Wassim Drira<br><br>