[SERVER-10924] Enterprise edition: rename default snmp config file from mongod.conf Created: 26/Sep/13 Updated: 10/Dec/14 Resolved: 23/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging, Usability |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sridhar Nanjundeswaran | Assignee: | Ernie Hershey |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB enterprise edition build |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When mongod is started with --snmp-master it looks for a config file of the name mongod.conf. The default config file we ship with our packages is also called mongod.conf and hence is confusing. We should rename to mongodsnmp.conf or something similar |
| Comments |
| Comment by Sridhar Nanjundeswaran [ 23/Dec/13 ] |
|
The issue has not completely gone away with |
| Comment by Eric Milkie [ 23/Dec/13 ] |
|
Yes, I think so. |
| Comment by Ernie Hershey [ 21/Dec/13 ] |
|
Isn't this covered by |
| Comment by Eric Milkie [ 16/Oct/13 ] |
|
This is tricky. The default behavior for net-snmp is to have a ".conf" file in /etc/snmp for each application, with the application's name as the filename. For example, a typical installation already has snmpd.conf and snmptrapd.conf for snmpd and snmptrapd. If we want it to search for a different config file, we'll have to present the application name differently when calling init_snmp(). I'm not sure what else that would affect. We could ship the config file with a different name and change the .md directions to rename the file when the admin copies it, but I don't think that's a good idea. |