Le lundi 21 avril 2008 à 10:05 +0200, Guillaume Desmottes a écrit :
Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
In the testbed in peabody, the list of peers seen from the server is
usually a superset of what we see from each individual mesh view.
Could be related
thanx,
thats exactly what i needed
On Tue, Apr 22, 2008 at 5:56 AM, Guillaume Desmottes
[EMAIL PROTECTED] wrote:
Le lundi 21 avril 2008 à 10:05 +0200, Guillaume Desmottes a écrit :
Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
In the testbed in peabody, the list of
Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
In the testbed in peabody, the list of peers seen from the server is
usually a superset of what we see from each individual mesh view.
Could be related to: #6883 #6884 #6888
It would be very useful if we could get the list
2008/4/19 Giannis Galanis [EMAIL PROTECTED]:
When connecting to a jabber server, how can we check the list of XOs that
are seen in the mesh view, or the analyze activity?
Is checking the gabble log the only way?
What records in the log indicate arrival or departure?
When testing with 50 or
Ar 18/04/2008 am 23:25, ysgrifennodd Giannis Galanis:
When connecting to a jabber server, how can we check the list of XOs that
are seen in the mesh view, or the analyze activity?
Is checking the gabble log the only way?
What records in the log indicate arrival or departure?
When
In the testbed in peabody, the list of peers seen from the server is
usually a superset of what we see from each individual mesh view.
It would be very useful if we could get the list shown by the analyze
activity, but from the console.
I believe it would easy to do that from the
When connecting to a jabber server, how can we check the list of XOs that
are seen in the mesh view, or the analyze activity?
Is checking the gabble log the only way?
What records in the log indicate arrival or departure?
When testing with 50 or 100 XOs connected it is often impractical to
