From owner-freebsd-questions@FreeBSD.ORG Wed Jun 10 09:01:05 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9340C106566C for ; Wed, 10 Jun 2009 09:01:05 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 6D5BF8FC1E for ; Wed, 10 Jun 2009 09:01:05 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n5A913XD065259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Jun 2009 02:01:03 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n5A913Qs065258; Wed, 10 Jun 2009 02:01:03 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA24796; Wed, 10 Jun 09 01:50:29 PDT Date: Wed, 10 Jun 2009 01:49:16 -0700 From: perryh@pluto.rain.com To: martin@dc.cis.okstate.edu Message-Id: <4a2f738c.vK+04C2hzxx8edYV%perryh@pluto.rain.com> References: <200906100204.n5A24J97018545@dc.cis.okstate.edu> In-Reply-To: <200906100204.n5A24J97018545@dc.cis.okstate.edu> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Control-Z the Sleep Signal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2009 09:01:05 -0000 Martin McCormick wrote: > Thanks to all. In this case, I made SIGTSTP have the > same effect in the program that CTRL-C does (SIGINT) so now > either signal makes the application remove the lock and quit > gracefully. To each his own, I guess. To anyone familiar with the usual Unix/Linux conventions, this response to ^Z is going to be thoroughly unexpected. Is there any reasonable way to do only the minimum cleanup need for the lock to be safely removed, and then suspend, reacquiring the lock when resumed?