[SERVER-1223] Mongod should not have to perform cleanup when doing mongod --install/--remove Created: 11/Jun/10 Updated: 11/Jun/10 Resolved: 11/Jun/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.4.2, 1.4.3, 1.5.0, 1.5.1, 1.5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Dearing | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
any windows environment |
||
| Participants: |
| Description |
|
When you install or remove mongod as a service, the standard shutdown sequence occurs as if mongod actually ran. Illustrated below. It should be ensured that mongod is not actually starting up, and then remove the calls to the mongod shutdown sequence. D:\justin's projects\mongo>db\Debug\mongod --remove D:\justin's projects\mongo>db\Debug\mongod --install |
| Comments |
| Comment by Justin Dearing [ 11/Jun/10 ] |
|
Mongo should not have opened any listening sockets, or opened any files. Running through the shutdown sequence when only interacting with the SCM seems to be slightly less overkill than doing so when running mongod -h. However, if you feel the checks are necessary, in case in scm interaction becomes more complicated I'll not push the issue further. |
| Comment by Eliot Horowitz (Inactive) [ 11/Jun/10 ] |
|
each piece closes the resources it may or may not have opened. |