CVS: Can I restrict the "cvs remove" to specific users?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
CVS: Can I restrict the "cvs remove" to specific users?
Hello all,
I'm an admin to a CVS server, but am still trying to pick up on some of the specifics.
Earlier this week, one in our group accidentally deleted several files to the attic. I checked out an earlier version and re-committed them, but I'd like to keep this from happening if possible.
Can I restrict the ability to use the "cvs remove" command to only specific users?
I'm positive this will happen again, and probably soon.
Any suggestions are welcome.
Believe me, I'd like to specify just-read or read/write access, but all of the current users need to be able to write to this repository, so I'm kind of stuck there.
I was hoping I could edit the commitinfo file, or one of the other CVSROOT files, so that it could check which user was trying to do a commit, and then allow/restrict them based on their user name.
since we use a managed passwd file for each repository they all get an email everytime someone commits a file.
i suppose if you can find the correct CVSROOT/file that could at least inform the masses when someone does this might do. Peer pressure keeps peeps from doing stupid stuff. LOL
I was reading something a little bit ago about someone who was running a script through the commit function but there were no links to what he had done and was very vague.
yea you can specify readers and writers with files
by just making files CVSROOT/readers CVSROOT/writers and putting the cvs user names in there
but if you want a writer to not be able to remove a file i think the sticky bit on the directory the files are in might do what you want
chmod a+wt
i think if you then setuid on that directory to you all the files that get created only you can delete
so then even if someone has write access to the folder only the files owner can delete it
that's kind of what sticky was dsigned to do -- i might have some of the details confused however-- i usually do
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.