We installed ADSM on a 2.5 machine, and start the GUI.  Before it displays the
GUI box, a message is displayed indicating a problem with the segmentation
file, and then takes a core dump.  We checked the wrapper file as described in
the attached note, and it was already set this way.

Has anyone else seen this problem?  How did you solve it?

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: ADSM client for Solaris 2.5
04-17-96 05:12 AM

Hi,

Solaris 2.5 has been officially accepted as a valid OS in our company
and we were (and still are) worried by ADSM support for this level.

We are running ADSM server on VM (V1R1L0.15) and the only version
installed for the client is V1R2.

I saw a recent posting about Solaris 2.5 and we investigated why ADSM
V1R2 was running on Solaris 2.4 but not on 2.5 !!

In fact the sun client works thru a wrapper script that then calls the
correct binary (Sunos or Solaris)... and I reproduced the fatal lines
killing 2.5 support in dsm.wrapper ....

(I Recall : Solaris 2.n = SunOS 5.n + ...)


ARCH=sun4
if [ -f /vmunix ]
then
  ARCH=`arch`
else
if [ `uname -r` = 5.3 ] || [ `uname -r` = 5.4 ]
  then
    ARCH=solaris

The uname test is really far too simple : when Sun will deliver a 2.6
Solaris or 2.7, ADSM client maintenance will be necessary to modify the
wrapper to support these new software levels.

The new test in V2 Client looks like :

if [ `uname -r` = 5.3 ] || [ `uname -r` = 5.4 ] || [ `uname -r` = 5.5 ]

And we get support for 2.5 !!!! impressive .. but not for a "generic"
2.n !!!!


The real question is about support of V1 clients : DO WE NEED to UPGRADE
all our clients to V2 ?? Is that clear that no other maintenance will be
done on V1 ADSM clients ?

Cheers, Michel

--
Michel Gaillard
Michel Gaillard
DSI/DPI
Alcatel CIT Velizy France
E-Mail: Michel.Gaillard AT vz.cit.alcatel DOT fr
Voice : (33.1) 30 67 32 56