[SERVER-27260] systemd service files should not start mongod with --quiet Created: 01/Dec/16 Updated: 06/Dec/17 Resolved: 07/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 3.0.14, 3.2.11, 3.4.0 |
| Fix Version/s: | 3.4.6, 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux with systemd init |
||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Backport Requested: |
v3.4, v3.2, v3.0
|
||||
| Participants: | |||||
| Description |
|
Both the rpm/mongod.service and debian/mongod.service systemd service files start mongod with the --quiet command line option. This is inappropriate because quiet mode is a user preference that, if desired, should be enabled in the config file. The older init scripts, including the init.d and upstart styles, start mongod with just the config file option (and have always done so). Thus the systemd service files should also start mongod with just the config file option. Having --quiet enabled by default like this means that valuable information about connection lifetimes is absent from logfiles, which can impede diagnosis of issues. |
| Comments |
| Comment by Githook User [ 15/Jun/17 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: (cherry picked from commit f08d5c4d04987c3723e852b43d2ebc921c818f4c) |
| Comment by Githook User [ 07/Jun/17 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: |