Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!ncc!lyndon@nexus.ca
From: lyndon@nexus.ca (Lyndon Nerenberg)
Newsgroups: comp.sys.next
Subject: Re: = An Imaginary Scenario =
Message-ID: <10514@ncc.Nexus.CA>
Date: 27 Oct 88 01:58:32 GMT
Article-I.D.: ncc.10514
References: <4192@pitt.UUCP> <12670004@eecs.nwu.edu> <4003@encore.UUCP> <10441@s.ms.uky.edu>
Sender: lyndon@ncc.Nexus.CA
Reply-To: lyndon@nexus.ca (Lyndon Nerenberg)
Organization: Nexus Computing Inc.
Lines: 21
In-reply-to: sean@ms.uky.edu (Sean Casey)

In article <10441@s.ms.uky.edu>, sean@ms (Sean Casey) writes:
>"Ok, you wanted me to type the "getethernodename" command?"
>"Right."
>"It doesn't matter which machine, does it?"
>"Type it at the machine you want to use the program from."
>"Do you mean that I can only use the program from that machine?"
>"Yes."
>"But what if that particular one is busy. They're all networked, you know."
>"Sorry, you'll only be able to use it from that machine."
>- click -

This was a problem with FrameMaker on Suns. Their (FrameMakers)
solution was to implement a "license server" process that runs
on your file server. The workstation contacts the license server
to register itself when you start your copy of Frame. If the number
of concurrently running copies of frame matches the limit on your
license, your copy goes into "demo" mode.

I like this solution, however I wonder how long it will be before
I start running out of system resources due to all these daemons
running :-)