Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

raw data directory-level permissions #28

Closed
sbailey opened this issue Jan 8, 2021 · 3 comments
Closed

raw data directory-level permissions #28

sbailey opened this issue Jan 8, 2021 · 3 comments
Assignees

Comments

@sbailey
Copy link
Contributor

sbailey commented Jan 8, 2021

Currently the raw data files have write permissions removed even from the desi-user owner to prevent accidental updates (good). However the directories themselves still have user write permission, meaning that the desi user could accidentally delete files or add files to raw data directories that are supposed to be frozen. I suggest that we remove write permission from all past directories, and update desitransfer to remove write permission from each new night just before it backs it up to HPSS. That way we have to be very purposeful about any future updates and are more safe from accidental deletions.

@weaverba137 weaverba137 self-assigned this Jan 8, 2021
@weaverba137
Copy link
Member

Purely for the record: I think I tried this in the past and for a reason I can't recall it was more trouble than it was worth. If nothing else it is worth testing and documenting why it is a pain, even if we don't end up implementing it.

@weaverba137
Copy link
Member

I am testing this as an addition to PR #41. I can say that removing user-write before the backup is triggered would significantly increase the algorithmic complexity of the code, if it worked at all. However if it is done at the last possible moment before the backup, then I think it will work. Still needs operational testing.

@weaverba137
Copy link
Member

Closed by #41.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants