Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!akguc!codas!mikel
From: mikel@codas.UUCP (Mikel Manitius)
Newsgroups: net.unix
Subject: Re: INFO-UNIX Digest  V1#161
Message-ID: <114@codas.UUCP>
Date: Tue, 1-Oct-85 20:05:19 EDT
Article-I.D.: codas.114
Posted: Tue Oct  1 20:05:19 1985
Date-Received: Thu, 3-Oct-85 07:27:37 EDT
References: <1575@brl-tgr.ARPA> <135@cithep.UucP>
Organization: AT&T Information Systems (SDSS) - Orlando
Lines: 24

> What's wrong with multiple accounts?  At Caltech students ( when I was one,
> anyway ),  were given one account for each class that required the use of
> a computer, plus one account for random use.  The class accounts were paid
> for by the department that the class was in.  This is a good way to teach
> students about managing temporary resources.  Someone who puts a bunch of
> large files on a class account so he will not be over quota on his personal
> account gets an interesting lesson at the end of the term...
> -- 
> 					Tim Smith
> 					ihnp4!cithep!tim

That's fine on large IBM machines, where the operating system is not
robust enough to provide a comfortable enviornemt (such was the case for
me using the Michigan Terminal System at Rensselaer Polytechnic Institute),
however, this is not needed on a unix system as you can create directories
for all your needs. If you start creating many accounts, you end up with a
humungous /etc/passwd, which by the way is scanned many many times per
minute on an active system, and you add to the overhead.


Mikel Manitius                AT&T Information Systems
{ihnp4!}codas!mikel           151 Wymore Rd. Rm: 420
(305) 869-2462                Altamonte Springs, FL
AT&T-IS ETN: 755              32714