From owner-freebsd-questions Mon Oct 23 12:34:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by hub.freebsd.org (Postfix) with ESMTP id 3BFEE37B479 for ; Mon, 23 Oct 2000 12:34:48 -0700 (PDT) Received: from froekjaerf@netscape.net by imo-d07.mx.aol.com (mail_out_v28.32.) id n.5.1855a7 (16234) for ; Mon, 23 Oct 2000 15:34:45 -0400 (EDT) Received: from netscape.com (aimmail06.aim.aol.com [205.188.144.198]) by air-in02.mx.aol.com (v76_r1.8) with ESMTP; Mon, 23 Oct 2000 15:34:45 -0400 Date: Mon, 23 Oct 2000 15:34:44 -0400 From: froekjaerf@netscape.net (Flemming Froekjaer) To: FreeBSD-questions@freebsd.org Subject: SIG codes > 128 allowed? Mime-Version: 1.0 Message-ID: <641C2F90.19430A3A.0F2A144B@netscape.net> X-Mailer: Franklin Webmailer 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In signal.h, more precisely the struct __siginfo, si_code is defined as an integer, but the same include file also defines the constant _SIG_MAXSIG, with a value of 128. Does this mean that FreeBSD won't allow signal codes above 128, or can you use the whole positive spectrum of an integer? The reason I ask is that I want to define a sighandler for every thread in a process. As you may know, threads share the parent process' signal handlers, so I'll need a unique signal code for each thread. I anticipate that the number of threads per process will be about a thousand. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message