Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
6e7726ec
Commit
6e7726ec
authored
May 30, 2018
by
Ben Bodenmiller
Committed by
Rémy Coutable
May 30, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add details on root flag related to no_root_squash
parent
8df2e8cf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
1 deletion
+3
-1
doc/administration/high_availability/nfs.md
doc/administration/high_availability/nfs.md
+3
-1
No files found.
doc/administration/high_availability/nfs.md
View file @
6e7726ec
...
@@ -25,7 +25,9 @@ options:
...
@@ -25,7 +25,9 @@ options:
errors when the Omnibus package tries to alter permissions. Note that GitLab
errors when the Omnibus package tries to alter permissions. Note that GitLab
and other bundled components do
**not**
run as
`root`
but as non-privileged
and other bundled components do
**not**
run as
`root`
but as non-privileged
users. The recommendation for
`no_root_squash`
is to allow the Omnibus package
users. The recommendation for
`no_root_squash`
is to allow the Omnibus package
to set ownership and permissions on files, as needed.
to set ownership and permissions on files, as needed. In some cases where the
`no_root_squash`
option is not available, the
`root`
flag can achieve the same
result.
-
`sync`
- Force synchronous behavior. Default is asynchronous and under certain
-
`sync`
- Force synchronous behavior. Default is asynchronous and under certain
circumstances it could lead to data loss if a failure occurs before data has
circumstances it could lead to data loss if a failure occurs before data has
synced.
synced.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment