HP3000-L Archives

March 2000, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Emerson, Tom # El Monte" <[log in to unmask]>
Reply To:
Emerson, Tom # El Monte
Date:
Mon, 6 Mar 2000 17:33:11 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
> -----Original Message-----
> From: Donna Garverick [mailto:[log in to unmask]]
> "Wyman, Alan" wrote:
>
> > Regarding running MPEX.PUB versus MAIN.PUB, on our system
> there is no
> > difference since MPEX.PUB.VESOFT is simply a symbolic link to
> > MAIN.PUB.VESOFT.  This means that a process is not created
> for MPEX prior to
> > creating the MAIN process.
>
> my understanding (from vladimir....) is that the new version
> of vesoft has
> changed 'mpex' into a link to 'main'.  why?  1) to avoid the
> extra process
> creation (as noted by alan); 2) to keep from breaking
> every(?) installed site
> that runs mpex by invoking 'mpex'.                   - d
>

Good to know -- as it is, it has now been 5 years since I worked for VESOFT,
and "at the time" "posix" and all it entailed was quite new, so the change
to make MPEX a link to MAIN obviously came after I had left the company.

As it turns out, however, I just checked our system and I see that the
stand-alone CM "mpex" shell-to-main still exists (and we are on a fairly
recent release), so whatever logic in the installation job that sets this as
a symlink did not take effect.  (most likely due to this being an
update-from-prior-release instead of a new install)  Obviously, now, I
should schedule some time to switch to this new methodology and decrease the
strain on our process table(s)... :)

Tom

ATOM RSS1 RSS2