From owner-freebsd-hackers Thu Oct 28 8:32:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2C3F115125 for ; Thu, 28 Oct 1999 08:32:29 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA14271; Thu, 28 Oct 1999 11:31:07 -0400 (EDT) Date: Thu, 28 Oct 1999 11:31:07 -0400 (EDT) From: Daniel Eischen Message-Id: <199910281531.LAA14271@pcnet1.pcnet.com> To: dbader@eece.unm.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: POSIX threads Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an application that uses SIGUSR1, but also POSIX threads. It > appears (?) that the user-level POSIX threads now incorporated into > FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I > have a threaded application, what signals are still available for use? No, the threads library that comes with 3.x/4.x does not use SIGUSR1 or SIGUSR2 for anything. It does use SIGPROF via setitimer for its internal scheduling mechanism, and SIGINFO to dump thread information (to aid debugging), but the other signals are available. Perhaps you're confusing libc_r with LinuxThreads which also runs under FreeBSD. I believe LinuxThreads uses SIGUSR1 and/or SIGUSR2. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message