Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 31 18:52:48 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.4 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 mA11qm4I024634 for ; Fri, 31 Oct 2008 18:52:48 -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 mA11jARB005651 for ; Fri, 31 Oct 2008 18:45:10 -0700 Message-Id: <200811010145.mA11jARB005651@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: restart Date: Fri, 31 Oct 2008 18:45:10 -0700 From: Bill Cheng Someone wrote: > The B-2-b) part in the guideline says differently. Please resolve the > confusion. > Thanks, > > type "shutdown" in the 2nd window > (node *09 should do a CHECK, which should be seen by > node *06) > (node *09 should notice that it has not received a > CHECK-response from a beacon node and delete its > init_neighbor_list and restart and rejoin the > network, it should put node *07 in its init_neighbor_list) > (after node *09 restarts, node *06 should do a CHECK, but > since it doesn't have a neighbor, it should not send > CHECK messages, then it should delete its > init_neighbor_list and restart and rejoin the > network, it should put node *07 or node *09 in its > init_neighbor_list) Since this is the grading guidelines, it does *not* describe everything is detail. So, where it said: > (node *09 should notice that it has not received a > CHECK-response from a beacon node and delete its > init_neighbor_list and restart and rejoin the Some details were skipped. Node *09 cannot get a CHECK response, so it restarts. After it restarts, it cannot connect to the node in its init_neighbor_list, it deletes the init_neighbor_list, and so on. -- Bill Cheng // bill.cheng@usc.edu On Fri, Oct 31, 2008 at 9:12 AM, Bill Cheng wrote: > Someone wrote: > > > On not receiveing a check response within the stipulated time or when > not > > able to connect to enough neighbors in init_neighbor_list file, we do a > > soft-restart so do we delete the init_neighbor_list file in the former > case > > also or in both cases? > > In the first case (CHECK failed), you should not delete init_neighbor_list > file. > > In the 2nd case (when you start/restart with init_neighbor_list > file and cannot find MinNeighbors number of neighbors), then you > delete init_neihbor_list file. > > > Also should the log file be deleted for these cases ? > > No. You only delete the log file when your node is started with > -reset. > > > Also, should we assume that the startup.ini that is going to be > provided, > > will be in the home directory? > > No. It can be anywhere. Even in /tmp. It's a commandline > argument, you just need to open the file. You don't need to > do anything special with the filename. After you've parsed > the file, you know the HomeDir of this node. > -- > Bill Cheng // bill.cheng@usc.edu