Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

14
  • 4
    Why not fix the bug in the logging code instead? Commented Sep 9, 2012 at 21:30
  • 5
    Victor, it's probably not a bug. If the disk the log lives on runs out of space, is that a bug in the logging code? Commented Sep 10, 2012 at 0:05
  • 5
    @Carson63000 - well, yes. The logs aren't being written, therefore: bug. Implement fixed size rotating logs. Commented Sep 10, 2012 at 0:36
  • 6
    This is the best answer imo, but it is missing one crucial aspect: security. There are some exceptions that occur as a result of the bad guys trying to f-up your program. If an exception gets thrown that you are unable to handle, then you cannot necessarily trust that code anymore. Nobody likes to hear that they wrote the code that let the bad guys in. Commented Sep 10, 2012 at 2:04
  • 3
    @detly: The disk can still run out of space, even if you implement fixed size rotating logs. Is it still a bug in the logging code? Commented Aug 15, 2013 at 17:50