From mboxrd@z Thu Jan 1 00:00:00 1970 X-Sympa-To: caml-list@inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p78J92Hl020985 for ; Mon, 8 Aug 2011 21:09:02 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgQGAHUzQE5auLfF/2dsb2JhbABDqBcHgUABAQU4QAEQCxgJFg8JAwIBAgFFBg0BBQICh2u+QoZHBKNs X-IronPort-AV: E=Sophos;i="4.67,338,1309730400"; d="scan'208";a="115305953" Received: from 0405ds1-vaer.0.fullrate.dk (HELO fw.fugmann.net) ([90.184.183.197]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 08 Aug 2011 21:08:56 +0200 Received: from [IPv6:2001:470:dc46:1:211:aff:fe80:620d] (trillian.fugmann.net [IPv6:2001:470:dc46:1:211:aff:fe80:620d]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fw.fugmann.net (Postfix) with ESMTPSA id 8AEB840068; Mon, 8 Aug 2011 21:08:55 +0200 (CEST) Message-ID: <4E403443.9070709@fugmann.net> Date: Mon, 08 Aug 2011 21:08:51 +0200 From: Anders Peter Fugmann User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11 MIME-Version: 1.0 To: "forum@x9c.fr" CC: caml-list@inria.fr References: <4E37EBA3.6040800@fugmann.net> <4E386A65.8080000@ens-lyon.org> <4E38E4F8.6020300@fugmann.net> <4E3A5109.9030002@fugmann.net> <56CD527B-3F34-4D32-8BDC-6C952F3D9BF3@x9c.fr> In-Reply-To: <56CD527B-3F34-4D32-8BDC-6C952F3D9BF3@x9c.fr> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Validation-by: anders@fugmann.net Subject: Re: [Caml-list] filename and line number. Hi Xavier, On 2011-08-04 15:03, forum@x9c.fr wrote: > Could you elaborate on what was missing, or buggy in Bolt? > As long as it fits with its design, I may try to fix it to suit your needs. When we tried bolt, the main issue was log rotation. We wanted to make sure that logs were rotated so they would not fill up all disk space. Bolt does indeed do log rotation, but the files created files by bold includes either timestamp or pid, which changes between program invocation. This makes to harder to see which file is the current, and leaves a lot of log files during development. We therefore decided to send all log to stdout, and capture it though a simple program that would reopen the file when it received SIGHUP. (Logging to stdout is also helpful when developing). As we no longer used Bolt for log rotation, we decided to leave bolt, keeping external dependencies down. If bolt had the ability to reopen the log file on SIGHUB (or a function to reopen the log file), we would probably still be using it. That combined with the ability to log to stdout when developing would make it very useful. Regards Anders Fugmann