From owner-freebsd-questions Mon Dec 17 18:43:53 2001 Delivered-To: freebsd-questions@freebsd.org Received: from catalyst.sasknow.net (catalyst.sasknow.net [207.195.92.130]) by hub.freebsd.org (Postfix) with ESMTP id 3E51F37B41A; Mon, 17 Dec 2001 18:43:47 -0800 (PST) Received: from localhost (ryan@localhost) by catalyst.sasknow.net (8.11.6/8.11.6) with ESMTP id fBI2jh915234; Mon, 17 Dec 2001 20:45:43 -0600 (CST) (envelope-from ryan@sasknow.com) X-Authentication-Warning: catalyst.sasknow.net: ryan owned process doing -bs Date: Mon, 17 Dec 2001 20:45:42 -0600 (CST) From: Ryan Thompson X-X-Sender: To: "Russell A. Khurshudian" Cc: "Crist J . Clark" , Freebsd-Questions Subject: Re: RCS: Allowing more users to make changes In-Reply-To: <001701c1876b$5bfea4f0$0200a8c0@qubit> Message-ID: <20011217203704.X14608-100000@catalyst.sasknow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Russell A. Khurshudian wrote to Crist J . Clark: > What type of permissions do i need to set? rw on the file and rwx > (group permissions) on the RCS and dir the file exists in? The directory housing the file, as well as the RCS directory, need to be writeable by all RCS users (making them all members of the same group is convenient for this... man 5 group). A good policy might be this one: ci * # Check in all files first! chgrp groupname RCS RCS/* chmod 0770 RCS # World doesn't need to read backups chmod 0664 RCS/* Of course, if, when you create the RCS directory in the first place, your primary group is "groupname", and you set your umask to 002, this will all be done for you. Note that when you check out a file without a lock (co filename) it will typically have permissions 444 (everyone read). If you obtain a lock (co -l filename) it should be writable by the current RCS user. What happens with *,v is RCS is careful to preserve the original file permissions. This is one way to do it that works. There are dozens of other policies you could adopt with RCS, that I can think of. If you have a LOT of users over complex directory structures, you might actually save some time and hassle with the more complex CVS. - Ryan -- Ryan Thompson Network Administrator, Accounts SaskNow Technologies - http://www.sasknow.com #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2 Tel: 306-664-3600 Fax: 306-664-1161 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message