Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hpfcso!hpfcbig!diamant
From: diamant@hpfcbig.SDE.HP.COM (John Diamant)
Newsgroups: comp.sys.hp
Subject: Re: Re: Monitor 6.5, How To Solve The Problem
Message-ID: <7540043@hpfcbig.SDE.HP.COM>
Date: 22 Oct 89 05:52:01 GMT
References: <1306@oce-rd1.oce.nl>
Organization: HP SESD, Fort Collins, CO
Lines: 21

> Around here, I've always had to compile copies using our source license.
> I would assume SE's do the same thing.  I suspect `monitor` only works
> "perfectly" when compiled on the machine its to be used for, and maybe
> thats why a single /usr/contrib/bin/monitor copy isn't possible.
> Some of the things monitor can provide seem awfully kernel/system
> dependent.

This is also not an official response, but I think I have a little more
specific info.  I've used monitor for a long time on several different
releases of HP-UX, and I have never had to recompile my own version.
What I did have to do is get the SE distribution binary for each new
HP-UX release.  SEs should have them available for each release of
HP-UX which is still supported.  It is dependent on kernel structures,
which is why a new versio is needed for each new HP-UX release, but
reconfigured kernels of the same release will work just fine.


John Diamant
Software Engineering Systems Division
Hewlett Packard Co.		ARPA Internet: diamant@hpfclp.sde.hp.com
Fort Collins, CO		UUCP:  {ihnp4!hpfcla,hplabs}!hpfclp!diamant