You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When editing files using q-cli, lock files are created to prevent items from being edited by the another person. These files exist in the same directory as the original item with the number of the item followed by .lck. For example, if I were to edit ce 40 the directory structure would look like this:
ce/
├── 40
└── 40.lck
The following permissions are expected:
-rw-r--r-- 1 campb303 ecnuser 0 Jan 19 16:32 40
-rw-r--r-- 1 campb303 ecnuser 0 Jan 19 16:32 40.lck
When gizmo created lock files, his permissions are set to 600 instead of 644 but I don't know why.
# Same for qedit and qtedit
-rw------- 1 gizmo ecnqueue 51 Jan 19 16:12 69.lck
When I, @benne238, other students and/or full timers create lock files permission get set to 644. I believe this issue is just with gizmo.
The text was updated successfully, but these errors were encountered:
gizmo told me he has his user's mask set to 0077 in his .bashrc file which explains the above behavior.
A potential solution here could be to change the live queue directory's group to ecnqueue and set a sticky bit to make all files in that directory group readable. Need to check with Sundeep and Curtis.
campb303
modified the milestones:
v1-proof-of-concept,
v2-production-ready-read-onlyFeb 5, 2021
When editing files using q-cli, lock files are created to prevent items from being edited by the another person. These files exist in the same directory as the original item with the number of the item followed by
.lck
. For example, if I were to edit ce 40 the directory structure would look like this:The following permissions are expected:
When gizmo created lock files, his permissions are set to 600 instead of 644 but I don't know why.
# Same for qedit and qtedit -rw------- 1 gizmo ecnqueue 51 Jan 19 16:12 69.lck
When I, @benne238, other students and/or full timers create lock files permission get set to 644. I believe this issue is just with gizmo.
The text was updated successfully, but these errors were encountered: