> 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... :-) Just suggestions. --ken _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
