This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Jeff re: > Nothing in the log, > But ... > ps -e |grep syslog > returns > > [ldm@ldm src]$ ps -e | grep syslog > semget: No such file or directory > semop: Invalid argument This indicates that the PATH for 'ldm' contains a directory in which the GEMPAK 'ps' command is found, and it is found before the system 'ps'. One should _always_ make sure that package-specific directories (e.g., ~ldm/bin, ~ldm/decoders, ~ldm/util, etc.) come at the end of one's PATH. This will avoid the unintended use of the GEMPAK 'ps' command in preference to the system one. Also, it is likely that once you change your PATH setting (may need to logoff and log back on!!), LDM's configure will run correctly. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: DRW-916040 Department: Support LDM Priority: Normal Status: Closed