|author||Joey Hess||2019-10-01 10:15:32 -0400|
|committer||Joey Hess||2019-10-01 10:15:32 -0400|
Diffstat (limited to 'doc')
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/isCopyOf_does_not_work_on_nfs_filesystem/comment_1_b1ffea063d9928889df17d9a8f3e8a5d._comment b/doc/forum/isCopyOf_does_not_work_on_nfs_filesystem/comment_1_b1ffea063d9928889df17d9a8f3e8a5d._comment
new file mode 100644
@@ -0,0 +1,22 @@
+ subject="""comment 1"""
+Your NFS server must have root squash enabled then. So any propellor
+properties that try to set the owner will fail (File.ownerGroup).
+It's entirely reasonable for properties to need to set the owner of a file.
+Many properties make files owned by a specific user and having them
+squashed to "nobody" would break their purpose.
+There's only one property in propellor that currently uses File.isCopyOf,
+and that property is in fact installing a user's configuration file, which
+needs to be owned by that user. So changing that property's behavior is
+So your options are, disable the NFS root squash, or avoid using propellor
+properties that set file ownership. If you wanted to make a variant of
+isCopyOf that didn't preserve permissions, we could perhaps look at adding
+that to propellor.