[SERVER-10989] --quiet flag does not suppress logged info messages for tools Created: 01/Oct/13 Updated: 11/Jul/16 Resolved: 23/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The --quiet flag suppresses some informational messages, such as those thrown from tool.cpp: "connected to: 127.0.0.1" Some tools seem to also throw informational messages using the log() function. These messages are not suppressed by the --quiet flag. In some cases, these messages are going to stdout when data is also being written to that stream, and could corrupt the data. mongodump --> with --quiet, this message goes to stdout: mongorestore --> with --quiet, these messages go to stdout: mongoimport --> with --quiet, these messages go to stdout Also related is a problem with mongofiles. Mongofiles seems to output some informational messages using cout. mongofiles --> with --quiet, these messages go to stdout done! |
| Comments |
| Comment by Shaun Verch [ 23/Oct/13 ] |
|
Should be resolved as part of |
| Comment by Samantha Ritter (Inactive) [ 01/Oct/13 ] |
|
Part of this issue is covered by 1. Informational messages are sometimes going to stdout instead of stderr, which risks corruption of data, but is covered by |