Return-Path: william@bourbon.usc.edu
Delivery-Date: Wed Sep 10 22:09:49 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 m8B59m3D030194
	for <cs551@merlot.usc.edu>; Wed, 10 Sep 2008 22:09: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 m8B59QL8028973
	for <cs551@merlot>; Wed, 10 Sep 2008 22:09:26 -0700
Message-Id: <200809110509.m8B59QL8028973@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: What to be done when ctrl+c is pressed
Date: Wed, 10 Sep 2008 22:09:26 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > I have a quick question:
  > What to be done (at both ends client and server) when ctrl+c is pressed?

For the server, <Cntrl+C> should be handled the same way
as SIGALRM.  For the client, you don't have to catch <Cntrl+C>.
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>