From owner-freebsd-questions@FreeBSD.ORG  Fri Sep 11 02:59:06 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 659AA106566B
	for <freebsd-questions@freebsd.org>;
	Fri, 11 Sep 2009 02:59:06 +0000 (UTC)
	(envelope-from jalmberg@identry.com)
Received: from smtp-gw30.mailanyone.net (smtp-gw30.mailanyone.net
	[208.70.128.56])
	by mx1.freebsd.org (Postfix) with ESMTP id 465268FC19
	for <freebsd-questions@freebsd.org>;
	Fri, 11 Sep 2009 02:59:05 +0000 (UTC)
Received: from mailanyone.net
	by smtp-gw30.mailanyone.net with esmtpa (MailAnyone extSMTP
	jalmberg@identry.com) id 1MlwLl-0004XB-GL
	for freebsd-questions@freebsd.org; Thu, 10 Sep 2009 21:59:02 -0500
Message-ID: <4AA9BCF0.6040003@identry.com>
Date: Thu, 10 Sep 2009 22:58:56 -0400
From: John Almberg <jalmberg@identry.com>
User-Agent: Postbox 1.0.0 (Macintosh/2009090801)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: reducing size of apache instances
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 02:59:06 -0000

My Apache 2.2 instances are running about 18 Meg each. I've been 
thinking about doing something to trim these down, and I think tomorrow 
is the day to take action. They are getting out of hand.

I've done a bit of research on this. I think the way to get started is 
to eliminate unused modules. Problem is, I know which ones I need, since 
I purposefully added them. I *don't* know which ones I don't need, if 
you see what I mean, since I inherited them from the default configuration.

I assume that some are critical to the basic operation of Apache. I am 
hoping I can google a list of these tomorrow. Obviously these I'll have 
to live with.

But what about the set that is left after I remove the ones the system 
needs, and the ones I need? How do I know which ones I can safely turn 
off? All I can think of is a trial and error process (i.e., turn them 
off one by one and see if anything breaks.)

Is there a better way?

-- John