Return-Path: owner-new-httpd
Received: by taz.hyperreal.com (8.6.10/8.6.5) id MAA01234;
 Thu, 8 Jun 1995 12:47:02 -0700
Received: from ooo.lanl.gov by taz.hyperreal.com (8.6.10/8.6.5) with ESMTP id
 MAA01219; Thu, 8 Jun 1995 12:47:00 -0700
Received: by ooo.lanl.gov
	(1.37.109.16/16.2) id AA119230780; Thu, 8 Jun 1995 13:46:20 -0600
From: Rob Hartill <hartill@ooo.lanl.gov>
Message-Id: <199506081946.AA119230780@ooo.lanl.gov>
Subject: Re: More on logging
To: new-httpd@hyperreal.com
Date: Thu, 8 Jun 95 13:46:19 MDT
In-Reply-To: <199506081943.OAA14118@sierra.zyzzyva.com>;
 from "Randy Terbush" at Jun 8, 95 2:43 pm
X-Organization: Theoretical Division, T-8. Los Alamos National Laboratory
X-Snail: LANL Theoretical Divi' T-8, MS B285, P.O Box 1663,
 Los Alamos NM 87545
X-Marks-The-Spot: Doh !
X-Url: http://nqcd.lanl.gov/~hartill/
X-Cessive-Use-Of-Headers: check
Mailer: Elm [revision: 70.85]
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> 
> > > If the logging process is the parent, then it should simply be
> > > passing a pointer to a log information structure for the child to
> > > fill in as it handles the request. 
> > 
> > doesn't that need shared memory ?
> 
> I suppose it does. As I mentioned in earlier mail, some of thes
> features probably can't be available to *all* UNIX variants.
> I admit that logging is an important one, but we can always
> leave the standard CLF in place for those.
> 
> Are there other ways besides SHMEM to accomplish this?

Yup, all children drop the info down a socket to the logging process :-)

--
Rob Hartill                           
http://nqcd.lanl.gov/~hartill/