reader
reader copied to clipboard
ericleasemorgan
Need a way for a user to delete a carrel
We need a way for a user to delete a carrel if they make one they don't want to keep or that is full of buggy output.
We need a way for a user to delete a carrel if they make one they don't want to keep or that is full of buggy output.
Who is "the user"? If it is one of Team Project CORD, then they are enabled to ssh to the machine, cd to /export/reader/carrels and do rm -rf my-carrel. Again, if too few people (us) are creating carrels, then there is little demand for us to create a GUI. Web-based interfaces are dangerous. --ELM
if you are a garden variety user like me, we literally don't have permissions to delete our own carrels on the filesystem whether we have a GUI or not, I guess I should say grant users permission over their own carrel files in the filesystem? and secondary problem, user artrhyno owns everyones' carrel files on the filesystemwhich is maybe not how we want it?
if you are a garden variety user like me, we literally don't have permissions to delete our own carrels on the filesystem whether we have a GUI or not, I guess I should say grant users permission over their own carrel files in the filesystem?
Natalie, I'm pretty sure all folks on our cluster machine have sudo privileges. Instead, try:
$ sudo rm -rf my-carrel
Similarly, I believe you are able to change permission of file with something like this:
$ sudo chmod -r 755 /export/cord/etc/contexts
Please give those things a whirl, and remember, we have so few "users". Really only you and me.
On Jun 8, 2020, at 10:21 AM, Natalie Meyers [email protected] wrote:
quit closing my tickets before a fix is in place.
They are not broken.
To delete a carrel, say for example, a carrel named foobar:
- ssh to the head node
- cd /export/reader/carrels
- sudo rm -rf foobar
Yes a CRUD interface to carrel creation is a good idea, but I believe there are too few people doing the C (create) to justify creating a GUI to do the R, U, and D.
@ericleasemorgan - my last pesty question, but using sudo effectively makes it possible for any user to delete any other users' carrel(s)? So if sudo is how we will solve for user-initiated delete we may also need a gentleman's agreement where we agree to only delete our own carrels? not each others' without asking first or some such thing? or we could change how DR writes user jobs and carrel file rights and ownership to the file system but that sounds like a much bigger effort than we're ready to tackle now?
I have been thinking about this, and I believe I/we can create a solution, but I'm still thinking. --ELM
