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

[LDM #YGA-963195]: Future LDM feature request



Gilbert,

> OK, problem found.
> 
> >N  1 address@hidden  Sat Jan  1 00:16  23/1100  "Cron
> <address@hidden> /bin/bash -l -c 'bin/ldmadmin check >check.log 2>&1' ||
> mailx -s '"ldmadmin check" problem LDM may "
> N  2 address@hidden  Sat Jan  1 00:31  23/1129  "Cron
> <address@hidden> /bin/bash -l -c 'wasReceived -f "WMO|NIMAGE|NGRID|NEXRAD3"
> -o 900' || /bin/mail -s 'NOAAPORT data h"
> N  3 address@hidden  Sat Jan  1 00:31  23/1100  "Cron
> <address@hidden> /bin/bash -l -c 'bin/ldmadmin check >check.log 2>&1' ||
> mailx -s '"ldmadmin check" problem LDM may "
> N  4 address@hidden  Sat Jan  1 00:46  23/1129  "Cron
> <address@hidden> /bin/bash -l -c 'wasReceived -f "WMO|NIMAGE|NGRID|NEXRAD3"
> -o 900' || /bin/mail -s 'NOAAPORT data h"
> 
> ...
> 
> N 25 address@hidden  Sat Jan  1 03:16  23/1100  "Cron
> <address@hidden> /bin/bash -l -c 'bin/ldmadmin check >check.log 2>&1' ||
> mailx -s '"ldmadmin check" problem LDM may "
> 
> Same problem as mine was: there is no "mailx" command on our system, just
> mail, so it bounced to LDM's inbox on that server. I had to fix that on
> all the servers on my system, and on Tyler's just now. It should be
> working, finally.

Non-standard systems give me gas.  :-)

> *******************************************************************************
> Gilbert Sebenste                                                     ********
> (My opinions only!)                                                  ******
> Staff Meteorologist, Northern Illinois University                      ****
> E-mail: address@hidden                                  ***
> web: http://weather.admin.niu.edu                                      **
> *******************************************************************************

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YGA-963195
Department: Support LDM
Priority: Normal
Status: Closed


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.