On Fri, Dec 14, 2001 at 02:22:52PM -0500, Gianni Johansson wrote:
> On Friday 14 December 2001 09:35, Toad wrote:
> > Hi. According to localhost:8889, my (severely borken) node has 9
> > references. The top 6 have CP = 1.0 and have never been contacted.
> Never successfully contacted or never trie
On Fri, Dec 14, 2001 at 02:22:52PM -0500, Gianni Johansson wrote:
> On Friday 14 December 2001 09:35, Toad wrote:
> > Hi. According to localhost:8889, my (severely borken) node has 9
> > references. The top 6 have CP = 1.0 and have never been contacted.
> Never successfully contacted or never trie
> > On Fri, Dec 14, 2001 at 10:39:51AM -0600, Edgar Friendly wrote:
> > > You don't get new noderefs by inserting.
> >
> > Yes, you do.
> >
> > --
> >
> You do? whose noderef do you get? some random person along the
> chain? That seems wierd.
Ive found that successfully inserting a small file i
On Fri, Dec 14, 2001 at 10:39:51AM -0600, Edgar Friendly wrote:
> toad writes:
>
> > On Fri, Dec 14, 2001 at 09:13:41AM -0600, Edgar Friendly wrote:
>
> > > The reason you have nodes with high CP that haven't been contacted is
> > > that fred already punished them (by not talking to them for a w
On Fri, Dec 14, 2001 at 09:13:41AM -0600, Edgar Friendly wrote:
> toad writes:
>
> > Hi. According to localhost:8889, my (severely borken) node has 9 references.
> > The top 6 have CP = 1.0 and have never been contacted. I am running with
> > debug logging, so I grepped my logs. Four of them don'
Hi. According to localhost:8889, my (severely borken) node has 9 references.
The top 6 have CP = 1.0 and have never been contacted. I am running with
debug logging, so I grepped my logs. Four of them don't appear at all, ever,
anywhere in the log (for today). Node has been running for about 8 hours
On Friday 14 December 2001 09:35, Toad wrote:
> Hi. According to localhost:8889, my (severely borken) node has 9
> references. The top 6 have CP = 1.0 and have never been contacted.
Never successfully contacted or never tried?
There's a time based recovery scheme that causes the CP of nodes that
On Fri, Dec 14, 2001 at 11:16:11AM -0600, Edgar Friendly wrote:
> > > You don't get new noderefs by inserting.
> >
> > Yes, you do.
> >
> You do? whose noderef do you get? some random person along the
> chain? That seems wierd.
The last node in the chain, except for datasource resets, just li
On Fri, Dec 14, 2001 at 10:39:51AM -0600, Edgar Friendly wrote:
> You don't get new noderefs by inserting.
Yes, you do.
--
:: tavin cole (tcole at espnow.com) ::
if there's been a way to build it
there'll be a way to destroy it
things are not all that out of control
-
Tavin Cole writes:
> On Fri, Dec 14, 2001 at 10:39:51AM -0600, Edgar Friendly wrote:
> > You don't get new noderefs by inserting.
>
> Yes, you do.
>
> --
>
You do? whose noderef do you get? some random person along the
chain? That seems wierd.
_
toad writes:
> On Fri, Dec 14, 2001 at 09:13:41AM -0600, Edgar Friendly wrote:
> > The reason you have nodes with high CP that haven't been contacted is
> > that fred already punished them (by not talking to them for a while),
> > and is trying to make sure they're still down. If we left their
toad writes:
> Hi. According to localhost:8889, my (severely borken) node has 9 references.
> The top 6 have CP = 1.0 and have never been contacted. I am running with
> debug logging, so I grepped my logs. Four of them don't appear at all, ever,
> anywhere in the log (for today). Node has been ru
12 matches
Mail list logo
