Hi Xavier,
On 2011-08-04 15:03, [email protected] 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
--
Caml-list mailing list. Subscription management and archives:
https://sympa-roc.inria.fr/wws/info/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
