[DOCS-3167] Suggestion for /manual/tutorial/install-mongodb-on-red-hat-centos-or-fedora-linux/ Created: 15/Apr/14 Updated: 11/Jan/17 Resolved: 11/Sep/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | bard.bloom@10gen.com | Assignee: | Michael Paik |
| 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, 22 weeks, 6 days ago |
| Description |
The last sentence is a bit rough. Consider something like "This tutorial outlines the steps to install MongoDB from .rpm packages"
It is not clear to the naïve reader whether the mongo-10gen package contains mongod and mongos or not, and whether one package or two must be installed. Even though this is made somewhat clear later, it's upsetting here.
I'm not sure about yum, but various package installers require me to answer y or yes to some questions. Does or might yum?
Comma splice.
After reading this section and following the "control scripts" link, I have no idea what, if anything, I'm supposed to do with control scripts. (I'd expect to see text like "These scripts tell MongoDB how to start and stop. If you want to change the location of MongoDB's data files from /var/lib/mongo, edit the control script foo and change the --dbpath parameter in the mongod command on line 384753945")
Why would I want to do that? What would such a script do? (As a Mongo expert, I'd expect an answer along the lines of "A typical mongos control script will start three mongos instances, giving them information in command-line arguments or configuration files about the replica sets in their sharded cluster")
For extra friendliness, I'd recommend adding a clause like "e.g., using the foo tool" here, if there is a standard tool to enable access to ports on SELinux.
Can this be changed?
For extra friendliness, consider adding a clause like "using a command like {{chown newuser /var/ {lib,log}/mongo}}". Or whatever we recommend doing, if chown isn't the right thing.
A naïve user who has never seen a MongoDB log file might well get upset here, wondering "What do I look for to tell if it's working?" A link to a "reading MongoDB log files" page might be helpful here, or, lacking that, a sentence to the effect that a running MongoDB log file tends to have waiting for connection or connection accepted messages towards the end, whereas a failed log file ends with shutdown messages and reasons why it failed. If you actually look at the log it's usually easy to tell, though I'm not sure how to communicate this to a naïve user. |
| Comments |
| Comment by Githook User [ 11/Sep/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 11/Sep/14 ] |
|
Author: {u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |