From d8a64611c43a4f1f5a129732f48aa656e94a4f68 Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Tue, 13 Dec 2022 16:16:49 +0000 Subject: [PATCH] --- ...Handling_permissions_in_a_shared_folder.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/Handling_permissions_in_a_shared_folder.mdwn diff --git a/doc/forum/Handling_permissions_in_a_shared_folder.mdwn b/doc/forum/Handling_permissions_in_a_shared_folder.mdwn new file mode 100644 index 0000000000..7c26a63b7a --- /dev/null +++ b/doc/forum/Handling_permissions_in_a_shared_folder.mdwn @@ -0,0 +1,17 @@ +Hi everyone, + +Just wanted to ask how to handle the following situation: + +- shared computer, everyone has an unprivileged, non-sudoer account and logs in via ssh for example or JupyterHub (unprivileged terminal, no `sudo` possible from there). +- shared directory (everyone in same group, all files owned by group, sticky bit, file owner varies) +- git-annex repository on this shared directory + +Problem: git-annex operations fail depending on who the owner of the files is. As git-annex needs to `chmod` files (which is only possible as owner of the file), this is a problem. + +A partial solution I've employed right now is to sudo-allow one specific command that recursively sets themselves as owner for the shared directory (including the git-annex repo). This however only works when `sudo` is working, which is not the case from JupyterHub... + +Any other ideas? (Except ditching the shared folder...) + +Cheers, + +Yann