Description
Given how useful the log file is, the server probably shouldn't default to erasing it. (This comes up in trainings a lot, that trivial operator errors can erase arbitrarily much useful historical information.) Could the server either default to logappend or try to rotate an existing log file on startup?
Attachments
Issue Links
- is depended on by
-
SERVER-4109 logappend should be the default
-
- Closed
-
- related to
-
SERVER-4797 automatically rotate mongo logs on a schedule or size threshold
-
- Closed
-