From owner-freebsd-current  Wed Aug 13 09:51:11 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA12191
          for current-outgoing; Wed, 13 Aug 1997 09:51:11 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12183
          for <current@FreeBSD.ORG>; Wed, 13 Aug 1997 09:51:05 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA18733; Thu, 14 Aug 1997 02:47:26 +1000
Date: Thu, 14 Aug 1997 02:47:26 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199708131647.CAA18733@godzilla.zeta.org.au>
To: ache@nagual.pp.ru, bde@zeta.org.au
Subject: Re: siginterrupt (was Re: Error in sleep !)
Cc: current@FreeBSD.ORG, sos@sos.freebsd.dk, terry@lambert.org
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I mean not application which uses some signal interface but initial
>handling of SIG_DFL _before_ any sigaction() or signal() used. I.e. is it
>safe per POSIX to have SA_RESTART for SIG_DFL action initially at
>application startup (before any application actions)? 

The initial value for sa_flags seems to be unspecified.  In practice, it
is 0 in FreeBSD.  This probably only matters if you use sigaction() to
find the old value and write a modified value, since SA_RESTART doesn't
affect SIG_DFL actions (it only affects caught signals).  It doesn't
matter for the other flags, since the "BSD default" for them is off.

Bruce