Return-Path: 
 <dev-return-73614-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org>
X-Original-To: apmail-httpd-dev-archive@www.apache.org
Delivered-To: apmail-httpd-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id AF5F59E4D
	for <apmail-httpd-dev-archive@www.apache.org>;
 Fri,  2 Dec 2011 18:53:44 +0000 (UTC)
Received: (qmail 68979 invoked by uid 500); 2 Dec 2011 18:53:43 -0000
Delivered-To: apmail-httpd-dev-archive@httpd.apache.org
Received: (qmail 68928 invoked by uid 500); 2 Dec 2011 18:53:43 -0000
Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:dev-help@httpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@httpd.apache.org>
List-Post: <mailto:dev@httpd.apache.org>
List-Id: <dev.httpd.apache.org>
Delivered-To: mailing list dev@httpd.apache.org
Received: (qmail 68920 invoked by uid 99); 2 Dec 2011 18:53:43 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Dec 2011 18:53:43 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rlandrito@gmail.com
 designates 209.85.161.173 as permitted sender)
Received: from [209.85.161.173] (HELO mail-gx0-f173.google.com)
 (209.85.161.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Dec 2011 18:53:37 +0000
Received: by ggnk1 with SMTP id k1so2167878ggn.18
        for <dev@httpd.apache.org>; Fri, 02 Dec 2011 10:53:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=7vcnNFPJqXk8kdXds426krUA5oWeMZgTNpr4LtwCzgw=;
        b=V/UPdKPJrK/KJlKg/UzAp8v8upbiTCSdd+4FL8JhTA3+lIKPMHOS3fC3oJS6I0ZYpV
         cf8szazRG9YtF/EcTk5as4YAYITSlDd258dqgmMuPDlTiQQuLOopMMcaqrz5zRss40UT
         K3viMXS0nraximODz3pYiWHM0haRr+fUJP5/c=
Received: by 10.68.13.101 with SMTP id g5mr16693241pbc.10.1322851996572; Fri,
 02 Dec 2011 10:53:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.147.10 with HTTP; Fri, 2 Dec 2011 10:52:55 -0800 (PST)
From: Rob Landrito <rlandrito@gmail.com>
Date: Fri, 2 Dec 2011 19:52:55 +0100
Message-ID: 
 <CAFsiBdACCjsCRtLubohz345TAbvZ4VG9JzuAbt3GuVu0cebtRg@mail.gmail.com>
Subject: htcacheclean and expired cache entries
To: dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=bcaec520ea27589bde04b3207b3b

--bcaec520ea27589bde04b3207b3b
Content-Type: text/plain; charset=UTF-8

Greetings,

I noticed that htcacheclean won't clean expired entries unless the
specified size limit is reached.  Is there any specific reason for this ?
 I'm looking into freeing up some inodes on some of my servers where the
total cache size hasn't reached my specified limit.  Would it be worthwhile
to add a switch to enable cleaning of expired entries even if the size
limit isn't reached ?

--bcaec520ea27589bde04b3207b3b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Greetings,<div><div><br></div><div>I noticed that htcacheclean won&#39;t cl=
ean expired entries unless the specified size limit is reached. =C2=A0Is th=
ere any specific reason for this ? =C2=A0I&#39;m looking into freeing up so=
me inodes on some of my servers where the total cache size hasn&#39;t reach=
ed my specified limit. =C2=A0Would it be worthwhile to add a switch to enab=
le cleaning of expired entries even if the size limit isn&#39;t reached ?</=
div>


</div>

--bcaec520ea27589bde04b3207b3b--