[SERVER-7294] Passing bad logpath to mongod/mongos should prevent server startup. Created: 08/Oct/12 Updated: 11/Jul/16 Resolved: 10/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.3.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Andy Schwerin | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Right now, passing a bad logpath just causes stdout to be used for logging, unless you launch mongod/mongos with --fork, in which case it terminates. It should always terminate if it can't use the specified logpath. |
| Comments |
| Comment by auto [ 10/Oct/12 ] |
|
Author: {u'date': u'2012-10-08T10:54:23-07:00', u'email': u'schwerin@10gen.com', u'name': u'Andy Schwerin'}Message: |