From owner-freebsd-isp Mon Sep 13 8:58:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.SKINNYHIPPO.COM (mail.SKINNYHIPPO.COM [216.25.13.94]) by hub.freebsd.org (Postfix) with ESMTP id 187CE1504B for ; Mon, 13 Sep 1999 08:58:30 -0700 (PDT) (envelope-from panda@skinnyhippo.com) Received: from egg [210.72.251.153] by mail.SKINNYHIPPO.COM (SMTPD32-5.05) id AF4B13A001D6; Mon, 13 Sep 1999 11:59:07 -0400 Message-Id: <3.0.5.32.19990914002139.00adfe90@mail.skinnyhippo.com> X-Sender: panda@mail.skinnyhippo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 14 Sep 1999 00:21:39 +0800 To: Dominik Brettnacher From: chas Subject: Re: managing huge log files. Cc: freebsd-isp@freebsd.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 05:11 PM 9/13/99 +0200, Dominik Brettnacher wrote: >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 That's what I was looking for ... > (e.g. >Webalizer) .. and that looks like just the ticket - very impressive. > - then you can rotate your logs daily or hourly while making >recent statistics from it. > >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. Thank you very much. chas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message