[Top][All Lists]

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

Re: File Permissions of new files.

From: stvnjns
Subject: Re: File Permissions of new files.
Date: Tue, 6 May 2008 09:34:13 -0700 (PDT)
User-agent: G2/1.0

On Apr 30, 6:08 pm, address@hidden (Larry Jones) wrote:
> Volker Katz writes:
> > I've read, that CVS sets the files' right according to the parent
> > directory's rights.
> No.  CVS expects the group id of a newly-created file to be inherited
> from its directory, but the permissions are not inherited.  That usually
> isn't a problem because if you don't have read/execute permission on a
> directory, you don't have any access to any of the files it contains, no
> matter what their permissions are.
> A new repository file's permissions are determined by the permissions of
> the user file it is being created from.  The user permissions are ORed
> into the group and other permissions, all write permissions are removed,
> and the permissions specified in $CVSUMASK are removed.  The user's
> umask is not used, only $CVSUMASK.  If it didn't work for you, it could
> be because you neglected to export it or because you're using a client/
> server access mode and had it set in the client's environment rather
> than the server's environment.
> -Larry Jones
> Nobody knows how to pamper like a Mom. -- Calvin

I think you may want to look at using the SGID command on the
directory.  This insures that newly created files remain
part of the upper directories group.  You will have to go in and
change all currently existing files back to the correct group, as the
SGID has no affect on existing files.

reply via email to

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