[DOCS-3170] Suggestion for /master/reference/program/mongod/ Created: 15/Apr/14 Updated: 13/Oct/14 Resolved: 13/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | bard.bloom@10gen.com | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | audit-2014 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 18 weeks, 2 days ago |
| Description |
I don't know what "manages data format" means. Maybe "manages data access"?
The point of this paragraph is a bit blurred. The options are useful on the command line for testing. The options themselves are crucial for controlling your database. The last sentence has a misplaced modifier: the configuration file, not the database, is fully capable.
Doesn't the -f option let you specify a filename too?
Make it clear that mongod writes its PID into the pidfile. It's only about 90% clear. It's like --logFile, but unlike --keyFile.
Is there some way to explain what the difference is between setParameter-based options and the generic command-line options described on this web page?
Why may it not be desirable for testing? (Answer, I guess, is that you can kill a non-forked mongo with control-c or some such from the shell.)
I don't know how to do this. It might be good to check that it's an obvious Kerberos thing, and, if not, to give a hint about how it is done.
Do we have a link about what the security implications are? This is scary without being helpful. Perhaps that is what we want, or perhaps we'd rather be both scary and helpful.
Consider rewriting to something like, "-
I didn't find much about the security implications by following the one link here. It would be good to link to something that actually describes them, so that the user can consider them based on something concrete.
Explain what <value> is — probably an integer, interpreted as a number of milliseconds.
1. The second sentence isn't literally true: mongod reports this percentage every four seconds. Consider combining the first two sentences to something like Forces mongod to log the percentage of CPU time in write lock, every four seconds. 2. The last sentence is confusing — does --cpu not use the standard choice of logging?
Shouldn't these be one sentence, not a fragment and a sentence?
You're not modifying the dbpath variable or value. You're modifying the data directory itself, creating subdirectories and moving files into them. The figure is clear enough, but the text is unclear.
I recommend adding the clause "on write operations" to the first sentence.
This should be i.e., (or viz.) not e.g.. e.g. means "for example", and the others mean "which is/namely"
This can be read to mean that id-only prevents mongod from loading any index. Consider rewriting as something like "Specify id-only to only load the -id index, or none to prevent the mongod from loading any index into memory"
Shouldn't this be something like --source <host>:<port>?
The paragraph "In the context..." is duplicated. One copy is probably enough.
By "clients" is it meant "clients which connect to this mongod instance?" |
| Comments |
| Comment by Githook User [ 13/Oct/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |