Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!batcomputer!theory.tn.cornell.edu!mqh From: mqh@theory.tn.cornell.edu (Mike Hojnowski) Newsgroups: comp.unix.admin Subject: Re: user-defined groups Keywords: groups Message-ID: <1991Mar20.164607.7452@batcomputer.tn.cornell.edu> Date: 20 Mar 91 16:46:07 GMT References: <1991Mar20.045739.27136@mp.cs.niu.edu> Sender: news@batcomputer.tn.cornell.edu Organization: Cornell Theory Center Lines: 18 Nntp-Posting-Host: theory.tn.cornell.edu > > For the kind of joint project you are talking about, I don't think your >world of 'networks of workstations with hundreds of users' is realistic. >Try a world of 'networks of hundreds of workstations, each with one or two >principle users.' For this type of setup, where the principle users >probably have root access to their own workstation, your solution is >far too complex. I disagree. We have a very similar need here. We will have a large system with >2000 userids. We may also eventually have a fleet of RS/6000's with a common uid space. Root privileges on these systems might be limited to our adminstrative group. It is always desirable to be able to distribute responsibility away from one system administrator with the keys to the city. We've come up with a solution using "expect" which allows us to have a group administrator for certain groups. Our solution still requires that a root user set up the administrator, and the group.