From owner-freebsd-isp Mon Sep 13 8:12:30 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dominik.saargate.de (dominik.saargate.de [212.88.132.246]) by hub.freebsd.org (Postfix) with ESMTP id 2709414C12 for ; Mon, 13 Sep 1999 08:12:26 -0700 (PDT) (envelope-from domi@saargate.de) Received: from localhost (localhost [127.0.0.1]) by dominik.saargate.de (8.9.3/8.9.3) with ESMTP id RAA63557; Mon, 13 Sep 1999 17:11:31 +0200 (CEST) (envelope-from domi@saargate.de) Date: Mon, 13 Sep 1999 17:11:31 +0200 (CEST) From: Dominik Brettnacher To: "panda@skinnyhippo.com" Cc: freebsd-isp@freebsd.org Subject: Re: managing huge log files. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 13 Sep 1999, panda@skinnyhippo.com wrote: > One of the websites I manage went ballistic 2 weeks > ago and has been producing 500+ MB of Apache logs > each day. May I ask how people are managing their > log files on high-traffic sites ? Use a log analyzer that brings its own history support with it (e.g. Webalizer) - then you can rotate your logs daily or hourly while making recent statistics from it. After that you can zip then or throw them away. Don't forget to give Apache a HUP, or better a USR1, so that it creates new log files when the old ones are moved to another directory. -- Dominik - http://www.saargate.de/~domi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message