On Thu, Jul 31, 2003 at 04:44:02PM -0700, Bryan Murdock wrote: > I have an application that a group of us are working on, it's under cvs, > and as soon as someone does a commit I want the updated files to be > copied to a certain globally accessible directory, so that people > immediately get the updated tool that we are working on. Rather than > create some new group for the three or four of us we though we could > just have me be the owner of the files in this global directory and use > a script that is run setuid as me. That way whoever does a commit > should have no problem overwriting the files in that global dir, but the > only way for anyone to overwrite those files is by doing a commit.
Sorry to reply twice to the same post. My last email was a rant about setuid and stuff. What I would actually do in this situation would be to set a group that the files in question belong to. It seems to me that the basic idea is that we want users X, Y, and Z, to edit a file, and not just the owner X. Groups handle that very nicely. Just set the directory to be setgid yourgroup and group-writable and you should be set.
pgp00000.pgp
Description: PGP signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
