[Info-vax] Setting Default Owner of a File
jbriggs444
jbriggs444 at gmail.com
Mon May 2 07:46:25 EDT 2011
On May 1, 12:34 am, Johnny Billquist <b... at softjar.se> wrote:
> On 2011-04-30 16:15, jbriggs444 wrote:
>
>
>
>
>
> > On Apr 30, 5:24 pm, gartm... at nonsense.immunbio.mpg.de (Christoph
> > Gartmann) wrote:
> >> In article<iphfmb$l4... at dont-email.me>, Chris Scheers<ch... at applied-synergy.com> writes:
> >>> It's been a while since I set up something like this, but if I remember
> >>> correctly, what I did was to make the directory owned by the GROUP, not
> >>> a user.
>
> >>> Then, set the protection on the directory so that it can be written by
> >>> members of the group.
>
> >>> That way, no privileges are needed.
>
> >>> [GROUP,*] is a valid user specification for most (all?) places that use
> >>> a user ID.
>
> >>> This was back in the VMS 5.x days, so it is possible that the details of
> >>> security inheritance have changed enough that this no longer works.
>
> >> Even if it does work, it won't solve the quota problem.
>
> > Why would it not solve the quota problem? If [group,*] is still
> > a valid owner for file and if group members still have ownership
> > rights to it then disk quota would work just fine.
>
> If the wish was that USERA should be charged for the quota, then how
> would this solve it?
If you put the problem that way, I agree that group ownership does not
solve it.
More information about the Info-vax
mailing list