I work on an HPC and often I have to share files with other users. The most approachable solution is to have an external cloud storage and recline back and forth. However there’s some projects that are quite heavy (several TB) and that is unfeasible. We do not have a shared group. The following is the only solution I found which is not to just set al permissions to 777, and I still don’t like it.

Create a directory and set ACL to give access to the selected users. This works fine if the users create new files in there, but it does not work if they copy from somewhere else as default umask is 022. Thus the only appropriate solution is to change default umask to 002, which however affects file creation system wide. The alternative is to change permissions every time you copy something, but you all know very well that is not going to happen.

Does it really have to be such a pain in the ass?

  • ag10n@lemmy.world
    8·
    3 days ago

    The fact that you’re sharing this internal policy stuff so openly is definitely a red flag.

    • ranzispa@mander.xyzOP
      2·
      3 days ago

      I don’t know what your background is, this is mostly hindrances when doing research. Administration has taken over and demands deciding how research should be conducted without having any idea on how it should be conducted.

      You may see it as a red flag, myself I have this very clear that I do not want to follow their bullshit. If I’m losing my job so be It, However you may be misunderstanding: I am not going to lose my job over this, nobody is getting hurt, and I am sharing a bureaucratic process that is fairly common over here in public institutions. This is not some large corporation that has to keep secret the time schedule of it’s workers: if you wish to come over I have full liberty of deciding to show you anything I have on my computer and most projects I am working on. Yes, there’s a couple things I can not show you, but everything else is my own job and up to me to show to whoever I wish. Institutions may retain part of the IP if we decide to commercialise stuff, but I am the author and I am free to share anything I don’t have an NDA on.

      I am afraid you come from a very different background and you are misunderstanding my situation.

      • nottelling@lemmy.worldEnglish
        3·
        2 days ago

        Your job as sysadmin is to adhere to your organization’s policy, no matter how stupid and hindering that policy might seem to you.

        You’re knowingly giving your users a workaround to their NDA, which puts all of your jobs and your data confidentiality at risk.

        You’ve got no business with root privileges.