summaryrefslogtreecommitdiff
path: root/doc/forum/Support_writing_as_owner__63__.mdwn
diff options
context:
space:
mode:
authordavid2019-03-05 00:29:41 +0000
committeradmin2019-03-05 00:29:41 +0000
commit82c693ebbf77b284901d68aba46576f9495d813a (patch)
tree84b2c9e9873f73ab4175d4553cbb7e2e69d6186c /doc/forum/Support_writing_as_owner__63__.mdwn
parent3f35474c24e08ddc081a2e16368483943784bcf2 (diff)
Diffstat (limited to 'doc/forum/Support_writing_as_owner__63__.mdwn')
-rw-r--r--doc/forum/Support_writing_as_owner__63__.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/Support_writing_as_owner__63__.mdwn b/doc/forum/Support_writing_as_owner__63__.mdwn
new file mode 100644
index 00000000..289536ce
--- /dev/null
+++ b/doc/forum/Support_writing_as_owner__63__.mdwn
@@ -0,0 +1 @@
+I have one propellor managed system where the home directory is NFS mounted, with `root_squash` enabled. This means that Ssh.authorizedKey fails with permission problems. On the other hand, root can su to the user in question. It seems like it might be possible for propellor (maybe even desirable?) to write files as the owner, rather than using chown.