Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Oct 9 19:26:31 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 m9A2QVMe011089 for ; Thu, 9 Oct 2008 19:26:31 -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 m9A2X990016838 for ; Thu, 9 Oct 2008 19:33:09 -0700 Message-Id: <200810100233.m9A2X990016838@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: CS551 - Final1 Date: Thu, 09 Oct 2008 19:33:09 -0700 From: Bill Cheng Someone wrote: > A few questions: > > -Does a Beacon node have to connect to all beacons and its init > neighborlist, or just its init_neighbor_list? If so after connecting to all > beacon nodes and neighbors would a beacon node just consider the > neighborlist as neighbors from that point? A beacon node does not have a init_neighbor_list file because it never performs a join. Since a beacon node is at the *core* of the network, it does not need to discover/join the network. > -Does a beacon node retry to connect to other beacon nodes only once after > the retry amount specified in the input file or does it keep trying with > that length gap until shutdown? It must never stop retrying! -- Bill Cheng // bill.cheng@usc.edu