[SERVER-1411] lockfilepath option is no good; need a pidfilepath option instead. Created: 13/Jul/10 Updated: 12/Jul/16 Resolved: 13/Jul/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.5 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Richard Kreuter (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Letting the user specify the lockfile's path is risky, since we use the lockfile as a sign of clean shutdown. So we need a separate pidfile that we don't use for anything. |
| Comments |
| Comment by Richard Kreuter (Inactive) [ 13/Jul/10 ] |
|
Fixed |
| Comment by auto [ 13/Jul/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Remove --lockfilepath option. |
| Comment by auto [ 13/Jul/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Add a --pidfilepath option, (next step: delete --lockfilepath). |