I recently had a configuration error regarding SSL, probably my own fault but that’'s beside the point right now.
This error flooded the admin-console.log with about 1Megabyte per second! Within 20 seconds the log-file was too big to be opened by most text-editors. Within a few hours (I hadn’'t noticed the error at first) parts of the server started to act weird. The admin-console.log file had become nearly 4GB and filled up the entire harddrive making it impossible for other deamons to have any temp storage, crippling all sorts of other functions this server has.
Wouldn’‘t it be wise to use some kind of circular logging making sure that (by default) logs don’‘t grow over 5MB (or any other sane amount that’'s still readable by common text-editors)? Furthermore, why not have continuous errors reported in the log once a minute, instead of 20 identical error-messages consisting of 10 lines each being written every second.
For the moment I’‘ve shut down Wildfire-server all-together because I’'m afraid the tiniest error might bring half the server down.
It won’‘t be hard to implement I can imagine and certainly wouldn’‘t hurt. What point is there in having a logfile that’‘s so big it can’'t be read?