From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26827 invoked by alias); 16 Jan 2009 17:19:13 -0000 Received: (qmail 26783 invoked by uid 48); 16 Jan 2009 17:19:03 -0000 Date: Fri, 16 Jan 2009 17:19:00 -0000 Message-ID: <20090116171903.26782.qmail@sourceware.org> From: "tom dot honermann at oracle dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20070704013541.4737.nmiell@comcast.net> References: <20070704013541.4737.nmiell@comcast.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/4737] fork is not async-signal-safe X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00101.txt.bz2 ------- Additional Comments From tom dot honermann at oracle dot com 2009-01-16 17:19 ------- The Austin group met yesterday and retained the decision to interpret fork as async-signal-unsafe with future specifications mandating that posix_spawn be made async-signal-safe to fill the functionality gap. Minutes of the meeting are available at https://www.opengroup.org/austin/docs/austin_446.txt. I think this bug can now be closed as "WONTFIX" -- http://sourceware.org/bugzilla/show_bug.cgi?id=4737 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.