From: Anders Peter Fugmann <anders@fugmann.net>
To: "forum@x9c.fr" <forum@x9c.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] filename and line number.
Date: Mon, 08 Aug 2011 21:08:51 +0200 [thread overview]
Message-ID: <4E403443.9070709@fugmann.net> (raw)
In-Reply-To: <56CD527B-3F34-4D32-8BDC-6C952F3D9BF3@x9c.fr>
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
next prev parent reply other threads:[~2011-08-08 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 12:20 Anders Fugmann
2011-08-02 12:45 ` Gabriel Scherer
2011-08-02 21:21 ` Martin Jambon
2011-08-03 6:04 ` Anders Fugmann
2011-08-03 7:10 ` Gabriel Scherer
2011-08-04 7:58 ` Anders Fugmann
2011-08-04 13:03 ` forum
2011-08-08 19:08 ` Anders Peter Fugmann [this message]
2011-08-09 16:31 ` forum
2011-08-03 19:57 ` Till Varoquaux
2011-08-03 20:52 ` Gabriel Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E403443.9070709@fugmann.net \
--to=anders@fugmann.net \
--cc=caml-list@inria.fr \
--cc=forum@x9c.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox