From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id B267EBC58 for ; Mon, 11 Oct 2010 15:54:24 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqsBABK0skzAbSoIe2dsb2JhbACDHpByjXwVAQEWIgQerW6SE4EigzJ0BIpB X-IronPort-AV: E=Sophos;i="4.57,314,1283724000"; d="scan'208";a="60904052" Received: from einhorn.in-berlin.de ([192.109.42.8]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Oct 2010 15:54:24 +0200 X-Envelope-From: oliver@first.in-berlin.de X-Envelope-To: Received: from siouxsie (e178004055.adsl.alicedsl.de [85.178.4.55]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id o9BDsNhR014695 for ; Mon, 11 Oct 2010 15:54:23 +0200 Received: by siouxsie (Postfix, from userid 1000) id E96D73758; Mon, 11 Oct 2010 15:54:22 +0200 (CEST) Date: Mon, 11 Oct 2010 15:54:22 +0200 From: oliver@first.in-berlin.de To: caml-list@inria.fr Subject: Re: [Caml-list] OPLP: Ocaml APache Log Parser Message-ID: <20101011135422.GC6256@first.in-berlin.de> References: <4CB3150D.6020402@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4CB3150D.6020402@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 X-Spam: no; 0.00; in-berlin:01 ocaml:01 parser:01 0100,:01 parser:01 bug:01 config:01 wrote:01 oliver:01 oliver:01 caml-list:01 parse:02 output:02 patches:03 let:03 On Mon, Oct 11, 2010 at 02:45:49PM +0100, Chris Yocum wrote: > Dear Everyone, > > I just wanted to let Ocaml'ers know that I am currently working on an > apache combined log parser. It is still in very early stages of > development but patches/comments/feature requests/bug reports are very > welcome. The code lives on github (http://github.com/cyocum/OPLP). [...] Aha... long ago I had done something similar, and it had an sql-like language for using it. The annoyance (and advantage ;)) with the apache logfiles is, that there are many "standard" formats, and you also can design your own output format. So it would make sense (I didn't do that) to parse the apache config files, and create a logparser from that information... Do you have planned to do this, or do you want to stick with some of the most used formats? Ciao, Oliver