[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000405: McIDAS-X checkout on newly installed SunOS 2.7 at Millersville

>From: David Fitzgerald <address@hidden>
>Organization: Millersville University of Pennsylvania
>Keywords: 200001262144.OAA16099 McIDAS-X 7.6 DSSERVE lock NFS MCDATA MCPATH 
>.mctmp link ps netstat hack


I took the liberty of logging onto your machines this morning to check out
the status of McIDAS-X.  I see that you have updated snowball to SunOS 2.7
and that you apparently were successful in doing some tests on McIDAS (?)

Since I had relinked the 7.604 distribution on your 2.6 system during
the many tests I ran, I felt that it was necessary to relink for 2.7:

<login as 'mcidas'>
cd mcidas7.6/src
touch *.o
make all

After verifying that the newly linked executables looked appropriate for

ldd df.k
        libgen.so.1 =>   /usr/lib/libgen.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libm.so.1 =>     /usr/lib/libm.so.1
        libF77.so.4 =>   /software/SUNWspro/lib/libF77.so.4
        libM77.so.2 =>   /software/SUNWspro/lib/libM77.so.2
        libsunmath.so.1 =>       /software/SUNWspro/lib/libsunmath.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2

(executables built on 2.7 will show use of /usr/lib/libgen.so.1; ones built
on 2.6 won't)

I decided to do some of the McIDAS checkout tests that were failing
previously.  Before getting to this, however, I did the following
on snowball:

rm .mctmp                (was a link to /tmp/mctmp)

After that, I started through the new build check out tests on twister:

setenv MCDATA /software/mcidas/mcidas7.6/data
setenv MCPATH ${MCDATA}:/software/mcidas/mcidas7.6/src
setenv PATH   /software/mcidas/mcidas7.6/src:$PATH
cd /software/mcidas/mcidas7.6/data

dmap.k AREA
---- --------- ------------ -------- ---------
-rw-   1503728 May 26  1998 AREA9010 /software/mcidas/mcidas7.6/data
-rw-   1503728 May 26  1998 AREA9011 /software/mcidas/mcidas7.6/data
-rw-   1543904 May 26  1998 AREA9012 /software/mcidas/mcidas7.6/data
-rw-   1003728 May 26  1998 AREA9013 /software/mcidas/mcidas7.6/data
-rw-   1003728 May 26  1998 AREA9014 /software/mcidas/mcidas7.6/data
-rw-    897680 May 26  1998 AREA9015 /software/mcidas/mcidas7.6/data
-rw-    608288 May 26  1998 AREA9016 /software/mcidas/mcidas7.6/data
-rw-    565512 May 26  1998 AREA9017 /software/mcidas/mcidas7.6/data
-rw-    311008 May 26  1998 AREA9018 /software/mcidas/mcidas7.6/data
-rw-    714288 May 26  1998 AREA9019 /software/mcidas/mcidas7.6/data
-rw-       768 Nov 25  1996 AREA9982 /software/mcidas/mcidas7.6/data
-rw-       768 Nov 25  1996 AREA9983 /software/mcidas/mcidas7.6/data
-rw-      2816 Jun 02  1998 AREA9995 /software/mcidas/mcidas7.6/data
9659944 bytes in 13 files

Things are looking good!

Then I ran code that was explicitly failing before:

dsserve.k ADD TOPO/CONF AREA 9011 9011 \"North America \(Conformal\)

Group/Descriptor         Type  Format & Range     RT Comment
------------------------ ----- ------------------ -- --------------------
TOPO/CONF                IMAGE AREA 9011-9011        North America (Conformal)
dsserve.k: done

(NOTE '"', '(', and ')' are escaped to avoid interpretation by the shell)

This demonstrates that McIDAS is now able to write files that are on
a file system NFS mounted from snowball.  Looks like the OS upgrade
got rid of the demons left over from the breakin you had last fall!

Things are really looking up now.  I believe that you can go ahead and
install McIDAS with assurances that the code will now run correctly
on twister.  Since I realize that this problem has put you into a serious
hole wrt time, please let me know if you need help with the remaining


>From address@hidden  Wed Apr  5 12:53:44 2000
>Subject: RE: 20000405: McIDAS-X checkout on newly installed SunOS 2.7 at 


Thanks for all your help.  I just tested and install McIDAS successfully,
and the configuration seemed to go well.  No more weird problems at least!


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.