> Ah, I see what you are getting at. A per-executable (or whatever)
> licensing/seat type deal? I don't know of any way to do this (aside from
> putting each binary to license into a separate directory?)
That defeats the purpose of 'max connections' then, doesn't it?
Essentially, what we want
At 00:26 10/11/99 -0500, you wrote:
>> Ah, I see what you are getting at. A per-executable (or whatever)
>> licensing/seat type deal? I don't know of any way to do this (aside from
>> putting each binary to license into a separate directory?)
>
>That defeats the purpose of 'max connections' then
At 12:26 AM 11/10/99 -0500, Ian Douglas wrote:
>> Ah, I see what you are getting at. A per-executable (or whatever)
>> licensing/seat type deal? I don't know of any way to do this (aside from
>> putting each binary to license into a separate directory?)
>
>That defeats the purpose of 'max connec
> >Does anyone have any ideas?
>
> tcpwrappers ???
Want to be a little more descriptive? How is that going to help me?
:~>>Essentially, what we want to perform is a network installation of large
:~>>commercial software products and restrict their use on the server by setting
:~>>a maximum number of connections. Currently, installing a copy of WordPerfect
:~>>on our server theoretically allows access to the program
Sorry, I misunderstood your original comment.
If a binary file is stored in a folder and that fodler is shared, then yes, in
theory, max connections should restrict the use. However, we're finding that
multiple workstations can access the binary files, thereby exceeding our
available licenses.
I
