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

19990225: several questions,

>From: Anthony Rockwood - MSCD Meteorology <address@hidden>
>Organization: Metropolitan State College of Denver
>Keywords: 199902251844.LAA14123 NTL GARP NWX

Tony-

>Here's a few questions I've been meaning to ask:
>
>1.  What are these core files that I see in /home/wxuser.  I see them in
>all the machines and they keep growing ?

These are created when GARP or NWX exits badly (core dumps). You should
delete them.  They do not keep growing.  They will  get replaced with
a new one each time the program coredumps.  There are two ways you can
keep these from being created:

1) In wxuser's .cshrc, add a line:

limit coredumpsize 0m

which will limit the size of a core file to 0Mb.

or:

2) Link the file core to /dev/null:

ln -s /dev/null core

so if a core file is created, it will go into the great bit bucket in
the sky.

The only problem is that the core file is useful for debugging problems.
If it is not created, then we can't run the debugger on it.  But, if
it is a persistent (repeatable) problem, then you can undo the limiting
of the core file and have one created.

>2.  In NWX, when I use the yesterday or day-2 option, some of the products
>cause NWX to quit.  For example, when I select MOS, NGM MOS, and day-2, I
>can bring up the current data by clicking its red box.  When I select
>'previous', it kills both NWX screens.  If I select PUBLIC PRODUCTS, STATE
>DISCUSSION, day-2, and select a station, it works fine and I'm able to use
>the 'previous' and 'next' buttons to go back and forward through all the
>discussions.  I haven't tried them all, but I know several other products
>will cause NWX to crash also.  It does this on all the machines.

You get the bug award for the week.  This seems to be a problem on
Linux, but not on other platforms.  You should not see this problem
on wxbox.  Chiz investigated and found some bad code where it was
freeing some memory and then setting the freed memory to a value.
He commented out the setting to a value, recompiled and it seems to
work now.  I put a new version of nwx on winfo2.  I also downloaded
it to mclap as nwx.new since it was turned on.  You need to go into
the $GEMEXE directory and move it into place (as gempak):

cd $GEMEXE
mv nwx nwx.bad
mv nwx.new nwx
chmod +x nwx

Let us know if the "fix" causes any new problems.  If it does not work,
just move nwx.bad back to nwx.

>3.  Is there any way to re-size the 'Text Report' screen in NWX so that I
>can move it up far enough to reach the 'previous' and 'next' buttons on
>both wxbox and mclap ?

NWX Window sizes are controlled by the file:

$NAWIPS/resource/Nwx

If you change the line (you can use pico):

Nwx*textwin.height:     600

to 

Nwx*textwin.height:     400

that would make the text window smaller.  There are other settings in
there you might want to consider changing (like the default position of
the window or the map window size).  Most of them seem pretty
self explanatory.  However, you should make a backup of this file
before mucking around too much in case you type a mistake.  Also,
remember that this file will get overwritten with a new release, so
back your changes up to something like Nwx.mclap

>4.  Is it possible to mount a directory on winfo (OS2 box) from winfo2
>(linux).  I've tried a few things but no luck. I'd like to generate some
>OS2 McIDAS products on winfo and have them on the web server on winfo2.

You will need to enable the NFS server.  In the TCP/IP Configuration
notebook, set nfsd up to be autostarted.  You will also need to export
the directory you want (c:\mcidas\data?) in the NFS tab.

Why not create the products on wxbox since that is already being mounted?
You have all the capabilities in McIDAS-X - scheduler, ROUTE post-process,
etc.  Eventually, winfo will go away and you will have to recreate all
these scripts elsewhere anyway.

Don