[Support #YER-489194]: Re: 20060120: 20060119: 20060118: 20060117: GEMPAK decoder installation

Gilbert,

I logged in to weather3 and saw that the LDM user does not have permission to 
look at the
gempak user account files:

% ls -l
total 40
drwxrwxrwx  21 ldm      users 4096 Feb  3 14:11 data
drwx------   6 gempak   users 4096 Feb  3 11:04 gempak
drwxr-xr-x   4 root     root  4096 Jan 15  2002 httpd
drwxrwxr-x  42 ldm      users 4096 Feb 15 01:01 ldm
drwxrwxr-x  34 mcidas   users 4096 Jan 26 15:13 mcidas
drwx------  10 sebenste users 4096 Feb  7 16:03 sebenste
drwxrwxrwx   3 ldm      users 4096 Dec  9 15:17 temp
drwxr-xr-x   3 root     root  4096 Jan 28 12:54 wxp

As the gempak user, I cd'd to /home and then "chmod 755 gempak".
This problem is just in the creation of the account, so as soon
as that change is made, the decoders that had been struggling
will start to work.

I added the GEMPAK log file rotation to the LDM account crontab entry- and 
copied
$NAWIPS/bin/dcrotatelog.csh to ~ldm/decoders for that action (since you
don't have a link from ~gempak/NAWIPS/Gemenviron to ~gempak/Gemenviron, I
edited the dcrotatelog.csh script to "source ~gempak/NAWIPS/Gemenviron".

Too late for the 18Z models today, but you should be able to start seeing 
watches and
warning in nmap2 now.

I'll log in to your other machines and make the same changes.

Steve Chiswell
Unidata User Support


Ticket Details
===================
Ticket ID: YER-489194
Department: Support GEMPAK
Priority: Critical
Status: Closed