Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Sep 4 09:00:21 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m84G0L6n023251 for ; Thu, 4 Sep 2008 09:00:21 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m84FwNI8005231 for ; Thu, 4 Sep 2008 08:58:23 -0700 Message-Id: <200809041558.m84FwNI8005231@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Child Process Id's Date: Thu, 04 Sep 2008 08:58:23 -0700 From: Bill Cheng Someone wrote: > As the child process will exit how the parent process will get to > know that any child process is no more in running state , > so that it can remove that child process id from the dynamic > array or list? There is a link in the spec pointing to a cs.utah.edu site on this. (Please look for SIGCHLD in the spec to find this link.) I've just added another link to a gnu.org site on a similar topic. Please try these out and see if they work. By the way, I don't usually emphasize SIGCHLD because, for a server like ours, I think it's best to use pthreads (although there is no penalty for using fork() for warmup #1). -- Bill Cheng // bill.cheng@usc.edu