From owner-freebsd-hackers  Wed Feb  5 08:20:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA01578
          for hackers-outgoing; Wed, 5 Feb 1997 08:20:46 -0800 (PST)
Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01523
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 08:20:38 -0800 (PST)
Received: from Mars.mcs.net (ljo@Mars.mcs.com [192.160.127.85]) by Mailbox.mcs.com (8.8.5/8.8.2) with ESMTP id KAA28504; Wed, 5 Feb 1997 10:20:37 -0600 (CST)
Received: (from ljo@localhost) by Mars.mcs.net (8.8.5/8.8.2) id KAA25043; Wed, 5 Feb 1997 10:20:36 -0600 (CST)
From: Lars Jonas Olsson <ljo@mcs.net>
Message-Id: <199702051620.KAA25043@Mars.mcs.net>
Subject: sigwait and threads?
To: hackers@freebsd.org
Date: Wed, 5 Feb 1997 10:20:35 -0600 (CST)
Cc: ljo@mcs.net
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 The "Threads primer" book by Lewis and Berg recommends using sigwait
for signal handling in multi-threaded applications. FreeBSD doesn't
have a sigwait though. Should we get one? Or is another method for
signal handling recommended?

 I've got a multi-threaded application that currently runs on SCO
UnixWare 2.1 that I also want to be able to run on FreeBSD. This
application uses sigwait and no signal handlers.

Jonas