Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  Apollo's Network License System (NLS)
Message-ID: <8811221429.AA01679@richter.mit.edu>
Date: 22 Nov 88 14:29:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21

Actually, I would have a problem with the NLS license server being
node locked. I run a fairly small (by Apollo's standard) network of
about 25 Apollos. We do a *lot* of development work over a wide
range of products. Many of these we would only want 1 or 2 concurrent
licenses which makes it a little unfeasible to distribute the licenses
over more than one NLS server. What if the server goes down? I don't
want to lose access to all of my software tools (FTN, CC, PAS, GMR, 3D
GMR, etc) just because a single node went down! If the registry can
be made immune to a single node failure, why can't the license server?
It is just as important to have access to the software as it is to
be able to login. If I can login but can't access the software, why
bother logging in?


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter@eddie.mit.edu
krowitz%richter@athena.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)