I got two answers to the question about Tru64 Ver 5.0A and MPIBIN
The general opinion was that the 3 attributes could be ignored as they
arent used in Ver 5.0A. The rm: subsystem is no longer used with the
MPI ( I knew about this a while ago)
It seems rather annoying ( and could cause potential panics in other
sysadmins) when you see these messages from install scripts. Surely by
now these test scripts should be able to tell the diffrence between OS
versions and what attributes are or are not required.
Tom said it looked like we had an outmoded kit when we installed
MPIBIN190 but it cam from our latest distribution set.
system administration account wrote:
>
> I don't have a 5.0A at hand right now, but from past experience I know that
> MPIBIN190 worked just fine for us on an ES40 with 5.0A PK1. I did not have
> to tune the kernel, however.
>
> Note the exact text of the messages you got:
>
> > Checking kernel configuration against suggested settings.
> > .......set-max-num = unknown attribute
>
> So the installation script runs "sysconfig -q ipc set-max-num", gets
> that error message, does something like
> /bin/test "unknown attribute" -ge 1024 || echo "*** Warning ***"
> (try it!), and there you are.
>
> > framework error: subsystem 'rm' not found
>
> I find that one slightly more scary. Ah, those shoestring shell scripts...
>
> > Should I be using MPIBIN190 with Tru64 Ver 5.0A? Or can I just ignore
> > the fact that thse attributes are unknown?
>
> Ignore the tuning advice. Don't bother trying to set those three attributes,
> since they really are unknown in V5.0A. (They exist in V4.0D, I just checked.)
"Dr. Tom Blinn, 603-884-0646" wrote:
>
> > Hi I am running MPIBIN190 on a GS140 running 5.0A patch set 1
> >
> > When I run setld -v MPIBIN190
> >
> > I get the follow ing message
> >
> > setld -v MPIBIN190
> >
> > Digital MPI V1.9 Binary (MPIBIN190)
> >
> > Copyright (c) Digital Equipment Corporation, 1995, 1996, 1997, 1998.
> > All Rights Reserved.
> > Starting the verification of
> > Digital MPI V1.9 (MPIBIN190)
> >
> >
> > Compiling an MPI test program ... Done.
> > Linking test program with the libmpi.a library ...
> > Link succeeded.
> >
> > *** The program however cannot be executed as root.
> > *** To test that the compiled MPI program runs successfully
> > *** (and prints an approximation of 'pi'),
> > *** you may, as a non-privaleged user:
> > > cd /tmp
> > > dmpirun -np 2 /tmp/mb_pi
> > > echo ok
> >
> >
> > MPIBIN190 IVP passed.
> >
> > Checking kernel configuration against suggested settings.
> > .......set-max-num = unknown attribute
> > *** Warning ***
> > The current kernel value of (ipc:) for set-max-num is lower
> > than the recomended limit of 1024.
> > vm-mapentries = unknown attribute
> > *** Warning ***
> > The current kernel value of (vm:) for vm-mapentries is lower
> > than the recomended limit of 200.
> > vm-vpagemax = unknown attribute
> > *** Warning ***
> > The current kernel value of (vm:) for vm-vpagemax is lower
> > than the recomended limit of 16384.
> > framework error: subsystem 'rm' not found
> > /usr/opt/MPI190/bin/check_params: test: argument expected
> > Verification of Digital MPI V1.9 (MPIBIN190) is complete.
> > #
> >
> >
> > Now I have edited the sysconfigtab and put in the entries for
> > set-max-num, vm-mapentries and vm-vpagelower ( even though they arent
> > mentioned in the sys_attrs(5) man pages). It is also documented in the
> > install notes to add these attributes. The machine was rebooted and
> > during the reboot those 3 attribute were flagged up on screen as
> > unknown.
> >
> > Should I be using MPIBIN190 with Tru64 Ver 5.0A? Or can I just ignore
> > the fact that thse attributes are unknown?
> > --
> > Gwen Pettigrew
> > Computer Officer
> > Department of Earth Sciences
> > Cardiff University
> >
> > http://www.ocean.cf.ac.uk/people/gwen
> > gwen_at_ocean.cf.ac.uk
>
> The version of the product kit you have is clearly not prepared to work
> correctly on Tru64 UNIX V5.x.
>
> If you query the subsystems in question and look at the defined names
> of the attributes, you may find that the attributes exist but that the
> names have underscores, not hyphens. This is a change that was made
> to get consistency among the various subsystems. If you can't find
> the right attribute, leave it out of the file. I suspect that the
> verification logic is also trying to check some other "vm" attribute
> but has a spelling error and is looking for an "rm" subsystem that
> doesn't exist any longer (and hasn't for a long time), which used to
> be related to the Memory Channel driver. But I can't tell.
>
> In any case, you've got an outmoded product kit there.
>
> Tom
>
Gwen Pettigrew wrote:
>
> Hi I am running MPIBIN190 on a GS140 running 5.0A patch set 1
>
> When I run setld -v MPIBIN190
>
> I get the follow ing message
>
> setld -v MPIBIN190
>
> Digital MPI V1.9 Binary (MPIBIN190)
>
> Copyright (c) Digital Equipment Corporation, 1995, 1996, 1997, 1998.
> All Rights Reserved.
> Starting the verification of
> Digital MPI V1.9 (MPIBIN190)
>
> Compiling an MPI test program ... Done.
> Linking test program with the libmpi.a library ...
> Link succeeded.
>
> *** The program however cannot be executed as root.
> *** To test that the compiled MPI program runs successfully
> *** (and prints an approximation of 'pi'),
> *** you may, as a non-privaleged user:
> > cd /tmp
> > dmpirun -np 2 /tmp/mb_pi
> > echo ok
>
> MPIBIN190 IVP passed.
>
> Checking kernel configuration against suggested settings.
> .......set-max-num = unknown attribute
> *** Warning ***
> The current kernel value of (ipc:) for set-max-num is lower
> than the recomended limit of 1024.
> vm-mapentries = unknown attribute
> *** Warning ***
> The current kernel value of (vm:) for vm-mapentries is lower
> than the recomended limit of 200.
> vm-vpagemax = unknown attribute
> *** Warning ***
> The current kernel value of (vm:) for vm-vpagemax is lower
> than the recomended limit of 16384.
> framework error: subsystem 'rm' not found
> /usr/opt/MPI190/bin/check_params: test: argument expected
> Verification of Digital MPI V1.9 (MPIBIN190) is complete.
> #
>
> Now I have edited the sysconfigtab and put in the entries for
> set-max-num, vm-mapentries and vm-vpagelower ( even though they arent
> mentioned in the sys_attrs(5) man pages). It is also documented in the
> install notes to add these attributes. The machine was rebooted and
> during the reboot those 3 attribute were flagged up on screen as
> unknown.
>
> Should I be using MPIBIN190 with Tru64 Ver 5.0A? Or can I just ignore
> the fact that thse attributes are unknown?
> --
> Gwen Pettigrew
> Computer Officer
> Department of Earth Sciences
> Cardiff University
>
> http://www.ocean.cf.ac.uk/people/gwen
> gwen_at_ocean.cf.ac.uk
--
Gwen Pettigrew
Computer Officer
Department of Earth Sciences
Cardiff University
http://www.ocean.cf.ac.uk/people/gwen
gwen_at_ocean.cf.ac.uk
Received on Fri Dec 15 2000 - 10:47:55 NZDT