From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4e81f7ee7f9152d03fb4d66e06c9c882@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] waitpid() From: Fco.J.Ballesteros In-Reply-To: <098cc449668fabc366ee4852e9cfbaff@proxima.alt.za> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-dlzlwcyabpdyyyjbfaubstdcbe" Date: Fri, 16 Apr 2004 13:10:23 +0200 Topicbox-Message-UUID: 5d28005e-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-dlzlwcyabpdyyyjbfaubstdcbe Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sorry. I meant the bsd waitpid and not the plan 9 waitpid. --upas-dlzlwcyabpdyyyjbfaubstdcbe Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Fri Apr 16 11:04:25 MDT 2004 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id C40F619D8D; Fri, 16 Apr 2004 05:04:14 -0400 (EDT) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id C040419D1F; Fri, 16 Apr 2004 05:04:11 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 51D1219D2B; Fri, 16 Apr 2004 05:03:25 -0400 (EDT) Received: from sparkle.iba.co.za (beam.iba.co.za [196.30.44.140]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 03E3419D1B for <9fans@cse.psu.edu>; Fri, 16 Apr 2004 05:03:23 -0400 (EDT) Received: from huddle.proxima.alt.za (prawn.iba.co.za [192.168.30.22]) by sparkle.iba.co.za (8.11.7/8.11.5) with ESMTP id i3G93JD09644 for <9fans@cse.psu.edu>; Fri, 16 Apr 2004 11:03:20 +0200 (SAST) Message-ID: <098cc449668fabc366ee4852e9cfbaff@proxima.alt.za> To: 9fans@cse.psu.edu Subject: Re: [9fans] waitpid() Organization: Proxima Research & Development From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.4.3(snapshot 20030221) (sparkle) Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: lucio@proxima.alt.za List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Fri, 16 Apr 2004 11:03:16 +0200 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: > The plan9 waitpid is a convenience for the case when you look for > a pid but don't care about others. Thus, I wouldn't vote for changing > the native interface; I'd just change ape, but only if posix says so. > Otherwise I'd fix the program using ape. I hope I'm not reading it wrong: P9 waitpid(2) is a stripped down version of wait(2) that returns only the "current" PID, no other details. It has nothing in common with Posix waitpid(). ++L --upas-dlzlwcyabpdyyyjbfaubstdcbe--