{"id":203,"date":"2019-01-14T12:55:36","date_gmt":"2019-01-14T17:55:36","guid":{"rendered":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/?page_id=203"},"modified":"2026-10-21T15:00:32","modified_gmt":"2026-10-21T19:00:32","slug":"sharing-directories","status":"publish","type":"page","link":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/docs\/file-storage\/sharing-directories\/","title":{"rendered":"Sharing Directories"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Making a Directory You Can Share With Members of Your Project<\/h2><\/div>

This document shows you how to make a directory and share it with members of your project in\u00a0 \/common\/users\/shared\/GROUPNAME<\/i><\/code>.<\/p>

Please remember that any files you store count against your \/common\/users\/NETID<\/i><\/code> quota. See Storage Technology Options<\/a> for the disk quota and information about our storage system.<\/p>

Here are the steps to follow:<\/p>

1. Create Appropriate Groups<\/strong><\/summary>

You’ll need to create a user group for your team. You can pick the group name. Please don’t use names starting with any of the following:
login, disabled, slide, cs, dept<\/code>.
These are reserved for system use. If you do, our software may take over without warning and drop you and your members.<\/p>

Recommendations for group names. (You can use some others, but these are safest.)<\/p>

    • Must start with a-z or _<\/li>
    • Characters after the first may also be digits or hyphens<\/li>
    • No longer than 32 characters<\/li><\/ul><\/li><\/ul>

      Here are the most common operations on groups with the group name GROUPNAME<\/em> using command lines.<\/p>

      – Create group: ipa group-add GROUPNAME<\/code>
      – Delete group: ipa group-del GROUPNAME<\/code> [you’ll get an error message, but the deletion still happens]
      – Add someone to the group (don’t forget to add yourself): ipa group-add-member GROUPNAME --users=NETID<\/code>
      – Remove someone from the group: ipa group-remove-member GROUPNAME --users=NETID<\/code>
      – To look at the group and its members<\/em>: ipa group-show GROUPNAME<\/code>
      – To see what groups you are in<\/em>: groups<\/code> [if you add someone to a group, they won’t see it until the next time they log in]
      – Another way to see information about yourself: ipa user-show NETID<\/code> [this may show groups that the groups<\/code> command doesn’t, because some groups are, in effect, invisible]<\/p>

      NOTE<\/strong>: The new group may be available for 15-20 minutes. Continue to Step 2 below once you know the group is available.<\/em><\/p>

      <\/details>
      2. Making a Shared Directory<\/strong><\/summary>

      Once you have a group for your team, here are the commands to make a shared directory. We have allocated a directory for sharing at \/common\/users\/shared<\/em> to simplify the process. We recommend you name the directory the same as your GROUPNAME<\/em>. Here are the steps:<\/p>

      mkdir \/common\/users\/shared\/GROUPNAME
      chgrp GROUPNAME \/common\/users\/shared\/GROUPNAME
      chmod 2770 \/common\/users\/shared\/GROUPNAME<\/code><\/p>

      Here’s what the commands do:<\/p>

      -The mkdir<\/code> command makes the directory in \/common\/users\/shared <\/em>with GROUPNAME.<\/em>
      – The chgrp<\/code> command sets it so your group can access the \/common\/users\/shared\/GROUPNAME<\/em>\u00a0directory.
      – The chmod<\/code> command sets the permissions to let your group members look at, create, and delete files in the directory. The leading two ensure that any files or subdirectories created inherit the group.<\/p>

      Verifying what was done using ls -ld<\/code>, the output should look like this:<\/p>

      drwxrws--- 2 NETID GROUPNAME 10 Sep 25 14:04 \/common\/users\/shared\/GROUPNAME\/<\/code><\/div>
      The critical part of the output is the drwxrws---<\/code> which gives the GROUPNAME<\/em> directory full access to GROUPNAME<\/em> members.<\/div>
      \u00a0<\/div><\/details>
      3. Setting Access to File Inside Shared directory<\/strong><\/summary>

      Any file you created in \/common\/users\/shared\/GROUPNAME<\/em> will be visible to GROUPNAME,<\/em> but it does not mean the file is readable or writeable to your group members. If you need everyone in the GROUPNAME<\/em> to be able to read\/write<\/strong> the file, you’ll have to make sure GROUPNAME<\/em> can do so. For suppose you want an existing file \/common\/users\/shared\/GROUPNAME\/file2share<\/em> to be set so that GROUPNAME<\/em> member can read\/write it, do the following:<\/p>

      cd \/common\/users\/shared\/GROUPNAME
      chmod 660 file2share<\/strong><\/code><\/p>

      Verify using ls -l .<\/code> The output should look like this:<\/p>

      -rw-rw<\/strong>---- 1 NETID\u00a0GROUPNAME 175 Sep 7 12:52 file2share<\/code><\/p>

      The critical part of the output is the second “rw”. That applies to other members of your group. The last three characters, “—” are for people not in your group without access to the file.<\/p><\/details>

      4. Accessing Files inside Share Directory<\/strong><\/summary>

      Now that you have created a shared folder, members of GROUPNAME<\/em> can access the files inside\/common\/users\/shared\/GROUPNAME<\/em> using the following command:<\/p>

      cd \/common\/users\/shared\/GROUPNAME<\/code><\/p><\/details><\/div><\/div><\/div><\/div><\/article><\/div><\/div><\/div><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

      Making a Directory You Can Share With Members of Your Project This document shows you how to make a directory and share it with members of your project in\u00a0 \/common\/users\/shared\/GROUPNAME. Please remember that any files you store count against your \/common\/users\/NETID quota. See Storage Technology Options for the disk quota and information about our storage […]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":463,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-203","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/pages\/203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/comments?post=203"}],"version-history":[{"count":50,"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/pages\/203\/revisions"}],"predecessor-version":[{"id":10926,"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/pages\/203\/revisions\/10926"}],"up":[{"embeddable":true,"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/pages\/463"}],"wp:attachment":[{"href":"https:\/\/wordpress.cs.rutgers.edu\/resources-cs-rutgers-edu\/wp-json\/wp\/v2\/media?parent=203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}