Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Oct 30 09:32:35 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 m9UGWZXl004609 for ; Thu, 30 Oct 2008 09:32:35 -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 m9UGiBcF009842 for ; Thu, 30 Oct 2008 09:44:11 -0700 Message-Id: <200810301644.m9UGiBcF009842@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: cs551 final1 Date: Thu, 30 Oct 2008 09:44:11 -0700 From: Bill Cheng Someone wrote: > On Thu, Oct 30, 2008 at 8:56 AM, Bill Cheng wrote: > > Someone wrote: > > > > > Two quick questions about final part1 > > > 1) Autoshutdown won't be changed by any event, right? > > > (e.g. restart won't reset autoshutdown) > > > > Correct! > > > > -------> > This node must therefore rejoin the network (delete its > init_neighbor_list file, gracefully shut itself down, and start itself > again as if it has never been part of the network) Should'nt this > restart the autoshutdown timer? No. > If a node with auto shutdown of 60 > seconds rejoins the network because it lost connectivity to core of > network at the 58th second, will it shutdown in 2 seconds? Yes. Just like warmup #1, the main reason for having autoshutdown is to make sure that you don't have a job running on nunki forever! -- Bill Cheng // bill.cheng@usc.edu