[SERVER-5478] mongosOptions and mongodOptions uses wrong parameter for logpath Created: 02/Apr/12 Updated: 06/Dec/22 Resolved: 25/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, Shell, Testing Infrastructure |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Both MongoRunner.mongodOptions and MongoRunner.mongosOptions use 'logFile' (which is not recognized by mongod) instead of 'logpath'. |
| Comments |
| Comment by Randolph Tan [ 25/Oct/21 ] |
|
Latest code in master already sets the value of logpath equal to logFile: |
| Comment by Geert Bosch [ 25/Oct/21 ] |
|
renctan Could you expand a bit on what the issue is here? Can we just close this? If not, what team do you think should own this now? |