Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 17 23:14:34 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9I6EYAx006910 for ; Fri, 17 Oct 2008 23:14:34 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9I6NBsa012127 for ; Fri, 17 Oct 2008 23:23:11 -0700 Message-Id: <200810180623.m9I6NBsa012127@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: CS 551 Final project #1 Date: Fri, 17 Oct 2008 23:23:11 -0700 From: Bill Cheng SOmeone wrote: > I have a question regarding InitNeighbors and MinNeighbors. (for eg when > InitNeighbors=3 and MinNeighbors=1 for a non-beacon node) When there is only > one beacon in the network and the non-beacon node comes up. It will get > join_reply only from this 1 beacon node. So as the neighbors it has is 1 > (less than InitNeighbors=3), shud it shut down itself after deleting the > init_neighbor_list file & come up again or should it continue to form a > connection with this beacon and if its successful (it will satisfy > MinNeighbors=1). During JOIN, if the non-beacon node cannot get enough join responses, it should print an error message and quit. It does not need to try again. -- Bill Cheng // bill.cheng@usc.edu