On Sat, Jul 05, 2003 at 01:50:23PM -0400, Ken T Takusagawa wrote: > > and the freenet.log has > > gone out of control and filled my disk a couple of times, this actually puts > > A simple (stop-gap) way of preventing (well, slowing) disk > filling might be to write the log to > java.util.zip.GZIPOutputStream. > > An even simpler way (for unix) would be to write the log to > stdout and pipe to gzip. > > A more complicated technique might roll the log every 10 MB > or something, and hope that the precise error you're > interested in didn't take place at the 9.999MB mark. > (Murphy would dictate otherwise... :-)
We have a patch from jrand0m to use the java 1.4 logging framework... I don't think this supports doing anything to the old logs, which is annoying, but it does support log rotation. Oh, and like the old logging code (but not the current code), if you run out of disk space it would deadlock the node... I am not sure that we aren't better off implementing our own log rotation. > > Just suggestions. > --ken -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
pgp00000.pgp
Description: PGP signature
