Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Oct 12 19:52:22 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 m9D2qMCd027567 for ; Sun, 12 Oct 2008 19:52:22 -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 m9D2xiR0022013 for ; Sun, 12 Oct 2008 19:59:44 -0700 Message-Id: <200810130259.m9D2xiR0022013@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Final Part 1 Date: Sun, 12 Oct 2008 19:59:44 -0700 From: Bill Cheng Someone wrote: > I am facing the exactly similar problem. I tried every possible > solution, but none worked. > When first node sends "hello" to second one, if second also sends > connect at the same time it says "Broken pipe". Debug, debug, debug! If you want to talk about this in detail, you can come to one of my office hours. -- Bill Cheng // bill.cheng@usc.edu Bill Cheng wrote: > Someone wrote: > > > I am getting a "broken pipe" error when connecting beacons with each > > other on parallel connections. > > For example, I have two beacons, the first one gets a connection request > > from the second one. The messages are exchanged. Now, the first one > > comes out of the retry mode and tries to connect to the second one. > > Connection is established successfully but when it tries to send to the > > second, I get the broken pipe error. What could be a possible reason for > > the same. I am trying this case to test in case of simultaneous > > connections. > > My code however runs fine when upon accepting a connection, I do not try > > to connect to the same port again. > > I don't know why this is happening. My guess is that > it's just a silly bug that's causing the problem! > -- > Bill Cheng // bill.cheng@usc.edu