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?

  • ranzispa@mander.xyzOP
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    Thanks, this is a great idea! I can see you have been doing this for a long time and you’re talking from experience. Regarding shared data: I use this more as a way to give raw data to other people and collect results from them. I use it mostly as a temporary directory used to transfer data, anything significant will get copied over to my share and backed up.

    I can see how you could be worried about storage quota, luckily I don’t have that many people to worry about. But it is funny you mention it as I could really see someone stashing a few conda environments in there just because they finished their inside quota…

    • blackbirdbiryani@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      If you’re not that worried about storage then you can just make copies if necessary, then you don’t really have to worry about permissions (apart from read, which is typically default for the same group). But yea if there’s any chance more than 1 person might work off the same copy of data on HPC, make it read only for the peace of mind. Regarding conda envs, yea I have a few common read only conda environments so that scripts can be used by multiple users without the hassle of ensuring everyone has the same env. Quite useful.