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.

Thanks.

the simple way is specifiying readers and writers.. to be more specific?... I'd have to read up but I dont think you can. I could be wrong though.

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.

Does make sense?
Thanks.

I'm not sure how you've got your setup but this is what im doing and our users are pretty happy. They just have to communicate well.

in loginfo i have this:

ALL /bin/mail -s '$USER modified REPOSITORY %{sv}' CVSUSERSMAILGROUP@domain.com

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