uabrc / uabrc/uabrc.github.io

Information shared with users when changes are made to members of a group

Open
#758 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

style: article/section 📝 system: cheaha 🖧 system: storage 🛢
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What would you like to see added?

The RC-Ops group includes information about a project folder when they make changes, following a ticket request;

  1. Create/rename a new project folder.
  2. Add a new user or remove an existing member of a project folder.

The information they share is generated with this command

ls -ld /data/project/<project or lab name>

The above command generates the below output

drwxrws--- 4 owner_BlazerID group_name 4096 Jul 11 07:23 /data/project/lab_name

Explanation for the output

File Type and Permissions (drwxrws---):

d: Indicates that this is a directory.
rwx: The owner (owner_BlazerID) has read (r), write (w), and execute (x) permissions.
rws: The group (group_name) has read (r), write (w), and execute (s) permissions. The s here indicates the setgid (set group ID) bit is set, meaning new files created within this directory will inherit the group of the directory.
---: Indicates others have no permissions.

Link Count (4):

This indicates the number of hard links to the directory. For directories, this includes the directory itself, its parent directory (..), and any subdirectories found in it.

Owner (owner_BlaxerID):

This shows the BlazerID of the owner of the directory.

Group (group_name):

This shows the group name associated with the directory. A group is a collection of user accounts that are used to define permissions and access controls on files and directories.

Size (4096):

The size of the directory in bytes. For directories, this typically reflects the space used by the directory structure itself, not the contents.

Modification Date and Time (Jul 11 07:23):

This indicates the last time the directory was modified. In this case, it was last modified on July 11th at 07:23.

Directory Name (/data/project/lab_name):

This is the path to the directory.

The output when shared with our users, is not understood. So we could include a little summary information to explain this. Something like;

"The output you can see in the previous mail means, only members of your group (mention name of group/members of group) can access the project folder (include path to project folder).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the documentation or operational guidance covering project-folder and group changes, including the ls -ld /data/project/<project or lab name> output. Confirm where the user-facing message is maintained, then add a plain-language summary identifying group access and the project-folder path; done means users can understand the shared output without interpreting Unix permissions themselves.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.