Skip to content

DOCS-10737: server parameter honorSystemUmask #3021

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

steveren
Copy link
Contributor

@steveren steveren commented Oct 16, 2017

This change is Reviewable

@steveren
Copy link
Contributor Author

Staged: https://docs-mongodbcom-staging.corp.mongodb.com/steverenaker/DOCS-10737/release-notes/3.6.html#mongod-options

For the release notes, I created a new section for new mongod options (since there are many in 3.6) and used the same formatting as currently exists for the new Sessions parameters. If it would be better to make a table with the option name on the left and a description on the right, let me know and I'll make it so.

@steveren steveren requested a review from kay-kim October 16, 2017 22:49
@kay-kim
Copy link
Contributor

kay-kim commented Oct 17, 2017

Ah -- this would for the present just go under the general enhancements.
We tend to subsection the key features -- sessions/(we'll have change streams)/agg ...
But for new options for mongod, if the new options are specific to some feature, then we'll group those instead of a section on new mongod options since some new options for mongod could be available in mongos and mongo shell. Close to when we have the bulk of things doc'ed, I think your sectioning probably is the way to go so that we list the options in couple of places on that page. But for now, could we just add a single bullet point under the general enhancements? That way, we can control when we do the reorging (vs. someone opening a ticket now going 'Hey, you haven't listed some of the new options under that section').

@steveren
Copy link
Contributor Author

Thanks Kay. Updated as you suggested.

@kay-kim
Copy link
Contributor

kay-kim commented Oct 17, 2017

merged! Thanks Steve.

@kay-kim kay-kim closed this Oct 17, 2017
mongo-cr-bot pushed a commit that referenced this pull request Apr 28, 2023
* DOCSP-29353 BACKPORT

* DOCSP-25925-migrationConcurrency (#2144)

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

* DOCSP-25925-migrationConcurrency

Co-authored-by: jason-price-mongodb <[email protected]>

* DOCS-15911-update-chunkMigrationConcurrency (#2604)

* DOCS-15911-update-chunkMigrationConcurrency

* DOCS-15911-update-chunkMigrationConcurrency

* DOCS-15911-update-chunkMigrationConcurrency

* DOCS-15911-update-chunkMigrationConcurrency

* DOCS-15911-update-chunkMigrationConcurrency

---------

Co-authored-by: jason-price-mongodb <[email protected]>

* DOCSP-29353 BACKPORT

---------

Co-authored-by: jason-price-mongodb <[email protected]>
Co-authored-by: jason-price-mongodb <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants