NSF Unidata

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

[GEMPAK #ZXE-379509]: semaphore issue

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 Joe,

You definitely want to run gpend after every instance of gdgrib if the program 
itself is being launched multiple times, such as in a loop - each one will be 
assigned a separate process ID and that's what is filling up your system's 
semaphores.

Give it a try with gpend called after each instance.  If you still see problems 
send the script along so I can take a look.

Best,

Michael

> 
> In our script, we're processing one GEMPAK file and extracting several
> Grib messages, so there's a loop running gdgrib. Do I need to run gpend
> after each iteration or just once at the end?
> 
> Thanks.
> 
> Joe
> 
> 


Ticket Details
===================
Ticket ID: ZXE-379509
Department: Support GEMPAK
Priority: Normal
Status: Open