Skip to content

Commit 2ace607

Browse files
authored
Remove ProtectHome from recommendations
In edge case, if user put nextcloud files under home of the selected user, this setting would cause them to be read-only. Normally for such cases we could use ReadWritePaths, but then we'd need to hardcode placement of the nextcloud files, which is unwanted. Better to remove this setting and it leave it up to the system administrators if they want to add further protection, the setting is not as critical as other anyway. Signed-off-by: Łukasz Domeradzki <JustArchi@JustArchi.net>
1 parent 5584f8a commit 2ace607

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

‎admin_manual/configuration_server/background_jobs_configuration.rst‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,6 @@ This approach requires two files: **nextcloudcron.service** and **nextcloudcron.
152152
ProcSubset=pid
153153
ProtectClock=yes
154154
ProtectControlGroups=yes
155-
ProtectHome=read-only
156155
ProtectHostname=yes
157156
ProtectKernelLogs=yes
158157
ProtectKernelModules=yes

0 commit comments

Comments
 (0)