-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
I think the most appropriate place is in the 3.0 release notes, but happy to defer to whatever is decided.
Then add a link or reference at http://docs.mongodb.org/manual/reference/program/mongotop/#cmdoption--locks
Right now the docs say
--locks returns an error when called against a mongod instance that does not report lock usage.
But it's not clear what kind of mongod instances don't report lock usage
- is related to
-
TOOLS-1849 Remove the mongotop --locks option
- Accepted
- related to
-
TOOLS-391 mongotop --locks with 3.0 mongod should show helpful error message and stop
- Closed