[ANN] Cyclic logs to help manage disk space issues with server logs

[ANN] Cyclic logs to help manage disk space issues with server logs

Post by apm3 » Fri, 06 Feb 2004 21:18:14


Several weeks ago I announced a GPL'd cyclic log package that allows
servers to record their stdout/stderr output to a cyclic file thereby
conserving disk space. C and C++ APIs are also provided. I have not
had any feedback yet. Do people feel this is not particularly useful?
Do people prefer to use syslog instead? I wrote it as a
platform-independent solution. I admit that a Unix-only server might
choose to use syslog instead for the extra facilities it has (e.g
routing, bunching repeated messages etc). I would be very interested
to know how Unix programmers typically deal with this issue. I would
also be interested to hear in how people have dealt with the issue
with Unix servers that are third party products. Do those products
tend to use syslog? What do you do if they write to stdout/stderr? I
found this to be a real problem when I was investigating a bug in (a
very old version of) the Orbix daemon. The daemon wrote to stderr in
debug mode (which we had to turn on to investigate the problem). The
diagnostic trace was VERY chatty. Cyclic logs then would have been
very useful.

Original annoucement:-
---
Cyclic logs provide a platform-independent way for a server to record
stdout and stderr such that the most recent information can be
retained in a logfile without such logfiles growing in size such that
they might fill the disk up. A cyclic log has a fixed size upon
creation and a structure that allows older data to be overwritten on
the arrival of new data to be logged. I have released a package to do
this on SourceForge at http://www.yqcomputer.com/
consists of a C++ library, a C library, a set of commands and a user
manual. It has been tested on Solaris, MS-Windows and Linux. It is
released under the GPL license. I hope it will prove useful for C++
and C projects. Feedback is welcome.