From owner-freebsd-current Wed Aug 13 11:35:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA18795 for current-outgoing; Wed, 13 Aug 1997 11:35:36 -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 LAA18787 for ; Wed, 13 Aug 1997 11:35:33 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id WAA18212; Wed, 13 Aug 1997 22:34:31 +0400 (MSD) Date: Wed, 13 Aug 1997 22:34:28 +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: <199708131822.LAA12815@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: > > So, it means that we still compatible with POSIX here. > > I'll change > > the default behaviour on FreeBSD > > to > > the default behaviour for signal(3) on FreeBSD > > to make siginterrupt(3) man page more clear. > > Still wrong. FreeBSD does not restart system calls by default. Hmm. What do you mean exacly in "by default"? When program use signal(3), it have restartable syscalls, but this case not covered by POSIX at all since there is no signal(3) in POSIX. When program use sigaction(2) with sa_flags == 0, it _not_ have restartable syscalls as POSIX requires. > I think it was a bad decision, but it's one required for a strict > POSIX environment. IMHO, we already are inside strict POSIX requirement in this area. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/