> And - however much of a "quagmire" things may turn out to be, I still
> reckon that GoGs make a more easily managed system overall. I
> personally would be quite happy with a restricted set of levels of
> hierarchy, to reduce spaghetti (e.g. 4). Ideally, I would like this to
> be under the control of admin - e.g.
> % pts set maxgoglevel 4
> maximum group hierarchy set to 4
> % pts set maxgoglevel 0
> Groups within groups NOT permitted.
Why not just a flag on each group, "may/may-not add groups"?
John
(Like MIT, we use Moria for all our group management, so we already get
groups-of-groups, etc. ... most handy ... insert cheap plug here:
pooh.cc> chlist -i -m -v egunzy
List: egunzy
Description: User Group
Flags: active, private, and visible
egunzy is a group with GID 8871
Owner: USER egunzy
Last modified by [EMAIL PROTECTED] with reg_svr on 21-aug-1992 16:51:25
USER:egunzy
pooh.cc> pts exam system:egunzy
Name: system:egunzy, id: -8871, owner: system:administrators, creator: sms,
membership: 1, flags: S-M--, group quota: 0.
pooh.cc> pts mem system:egunzy
Members of system:egunzy (id: -8871) are:
egunzy
-------------------------------------------------------------------------------
John Hascall ``An ill-chosen word is the fool's messenger.''
Systems Software Engineer
Project Vincent
Iowa State University Computation Center + Ames, IA 50011 + 515/294-9551
