Return-Path: william@bourbon.usc.edu Delivery-Date: Sat Oct 25 20:13:15 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 m9Q3DFK6025192 for ; Sat, 25 Oct 2008 20:13:15 -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 m9Q3NkjU007189 for ; Sat, 25 Oct 2008 20:23:46 -0700 Message-Id: <200810260323.m9Q3NkjU007189@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: CS 551 Date: Sat, 25 Oct 2008 20:23:46 -0700 From: Bill Cheng Someone wrote: > When we enter the status command at the prompt of a particular node A should > the nam file created contain the link information between B and C if A, B > and C are all connected to each other? Yes. The status request message is flooded to the whole network. So, node A should get the topology of the whole network and write that information to the nam file. -- Bill Cheng // bill.cheng@usc.edu