Return-Path: owner-new-httpd
Received: by taz.hyperreal.com (8.6.10/8.6.5) id OAA16419;
 Tue, 28 Mar 1995 14:03:08 -0800
Received: from ns.elsevier.nl by taz.hyperreal.com (8.6.10/8.6.5) with ESMTP
 id OAA16413; Tue, 28 Mar 1995 14:03:06 -0800
Received: from www.elsevier.co.uk by ns.elsevier.nl with SMTP (PP);
          Wed, 29 Mar 1995 00:02:20 +0200
Received: by www.elsevier.co.uk (4.1/SMI-4.1)	id AA27846;
          Tue, 28 Mar 95 22:59:40 BST
Date: Tue, 28 Mar 95 22:59:40 BST
From: Andrew Wilson <andrew@www.elsevier.co.uk>
Message-Id: <9503282159.AA27846@www.elsevier.co.uk>
To: new-httpd@hyperreal.com
Subject: <defunky>
Sender: owner-new-httpd@hyperreal.com
Precedence: bulk
Reply-To: new-httpd@hyperreal.com


Ahem,

	so, suppose you had:

epprod# uname -a
SunOS epprod 4.1.3_U1 2 sun4m
epprod# 

and you had a section in your Makefile that read:

# For SunOS 4
#AUX_CFLAGS= -DSUNOS4
# For Solaris 2. NOTE: Lots of problems have been identified with compiling
# httpd under Solaris. Use with caution. If you see aberrant behavior with
# httpd under Solaris 2, please mail us.
AUX_CFLAGS= -DSOLARIS2

and you typed:

make

and, later on, you complained, at length, that there were <defunct> processes
hanging about on your gear.  Well, wouldn't *you* be too embarrassed to admit
it?  I'm sure I would be, .. if it ever happened to me.

Perhaps one of the many interesting things that we could include in the 'FAQ'
is a line saying something like:

	If you see lots of <defunct> processes sitting on your server
	then check that you've compiled using the right architecture
	flag.  Compiling as Solaris2 on a SunOS box produces the
	same effect!

Ay.

[shuffles off, stage left, to howls of derisive laughter...]