Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 69779 invoked by uid 500); 14 Sep 2002 17:36:24 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 69766 invoked from network); 14 Sep 2002 17:36:24 -0000 Date: Sat, 14 Sep 2002 10:36:27 -0700 From: Aaron Bannert To: dev@apr.apache.org, dev@httpd.apache.org Subject: Re: Weirdness regarding that Jaguar setpgrp autoconf test Message-ID: <20020914173627.GB2528@clove.org> Mail-Followup-To: Aaron Bannert , dev@apr.apache.org, dev@httpd.apache.org References: <200209140113.VAA08709@devsys.jaguNET.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209140113.VAA08709@devsys.jaguNET.com> User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, Sep 13, 2002 at 09:13:13PM -0400, Jim Jagielski wrote: > Unfortunately, I've confirmed with APR that if autoconf tests > setprgp(1,1), results in: > > checking whether setpgrp takes no argument... yes > > whereas with setpgrp(0,0) it returns 'no' as it should (setpgrp > under Darwin *does* take an argument). So the bug report actually > *is* valid... autoconf.m4f should use setpgrp(0,0) The reason this is probably not a problem at all for Apache on Darwin is because we just use setsid() instead. -aaron