From owner-freebsd-current Wed Aug 13 13:17:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA25134 for current-outgoing; Wed, 13 Aug 1997 13:17:04 -0700 (PDT) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA25128 for ; Wed, 13 Aug 1997 13:16:58 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id AAA19999; Thu, 14 Aug 1997 00:15:33 +0400 (MSD) Date: Thu, 14 Aug 1997 00:15:29 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Terry Lambert cc: bde@zeta.org.au, current@FreeBSD.ORG, sos@sos.freebsd.dk Subject: Re: siginterrupt (was Re: Error in sleep !) In-Reply-To: <199708131950.MAA12930@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Terry Lambert wrote: > Without you specifically calling siginterrupt() to toggle SA_RESTART > from off to on (default is off), or calling sigaction() to set the Oh, no. siginterrupt() affects signal() only and default is _on_ for signal(). siginterrupt() not affects sigaction() at all. > What if you call neither sigaction(), nor signal()? What if you > call sleep(3)? What behaviour does it have? That's the point... As Bruce already says, only catched signals affects syscalls (restartable or not), so you must to call either signal() or sigaction() to have signal catched. POSIX requirement not affects SIG_DFL action. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/