[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Remote repository permissions best practices

From: Todd Denniston
Subject: Re: Remote repository permissions best practices
Date: Mon, 28 Mar 2005 16:57:23 -0500

[top posting as a courtesy for Doug]
"-R     Recursively change permissions of  directories  and
              their contents."

Its the "their contents" part that is the problem, you only need and want to
change the ownership and permissions on the directories.

The files should be read only, and we don't car who owns them.

Doug Lee wrote:
> On Mon, Mar 28, 2005 at 04:05:51PM -0500, Todd Denniston wrote:
> > BTW, as you currently have a repo, you may need to walk the whole existing
> > repository tree and do something like:
> > (assuming no spaces in your directory names, and you use this at your own
> > risk)
> > cd $CVSROOT/
> > chown :projectUNIXgroup project/
> > chmod g+sw project/
> > for i in `find project -type d`
> > do
> >  chown :projectUNIXgroup $i
> >  chmod g+sw $i
> > done
> What's the matter with
>         cd $CVSROOT
>         chown -R :projectUNIXgroup .
>         chmod -R g+sw .
> assuming constant :projectUNIXgroup and no need for different
> permissions anywhere under $CVSROOT.  I wonder in particular if a
> subsequent reset of owner/perms in $CVSROOT/CVSROOT would be in order.
> I think -R is standard for both chown and chmod now, but a couple of
>  `man' checks on the target system wouldn't hurt.--
> --
> Doug Lee           address@hidden
> Bartimaeus Group   address@hidden
> "Innovation is hard to schedule." -- Dan Fylstra

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]