framemaker installation
Bill Palenske
xxwrp at picasso.lerc.nasa.gov
Thu Mar 7 07:54:18 AEST 1991
Preface: I don't know much about how FrameMaker functions.
Pardon any malapropisms.
It's been suggested to me that I install FrameMaker (SGI) on a
non-SGI platform that serves as a disk farm ( Call this machine
DF ). I gather that the impetus behind this suggestion was that
DF would then function as our license server. The following
quote from the release notes seems to be pretty clear that
this cannot be done.
The license server host is the machine that runs the
license server _process_. It can be any machine; it does
not have to be the machine on which you have installed
the FrameMaker files ( the installation machine ).
I guess then that a followup suggestion may be: why not put
the FrameMaker software on DF and nfs mount it on some SGI which
would function as our license server. I suppose this could be
made to work. I'm not enthusiastic about this proposal. It seems
like a lot of bother. Moreover, it would probably considerably
complicate matters vis-a-vis host ids and getting passwords.
The problem is we have a disk space crunch on most of our SGIs
( we're looking at getting some more disks, but that is quite a
ways down the line. ) I do have one SGI that has enough space
and which I would like to make the license server, but it is
frequently used for special processing and I am reluctant to take
too many cycles away from that. My question here is: how does the
license server work? Is it a deamon which will be quiescent/sleeping
most of the time or what?
Finally, from reading the release notes it is not clear to me how
_client_ machines are set up to use FrameMaker. Does one nfs mount
things from the license server, install actual binaries on clients,
what?
Email will do. Thanks.
More information about the Comp.sys.sgi
mailing list