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

20020411: ldmadmin watch - binary output?

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.

  • Subject: 20020411: ldmadmin watch - binary output?
  • Date: Thu, 11 Apr 2002 15:10:36 -0600
>From: Joe Van Andel <address@hidden>
>Organization: National Center for Atmospheric Research
>Keywords: 200204111953.g3BJrna11948 LDM ldmadmin

Joe,

>Is there any good reason why the output of "ldmadmin watch" includes 
>null bytes (0x00)?  It makes it harder to use standard Unix tools like 
>'egrep', because 'egrep' thinks it is looking at a binary file, and 
>won't show matches.

'ldmadmin watch' simply runs the LDM program pqutil with explicit
setting of the feed as ANY and the action to watch the default queue:

elsif ($command eq "watch") {   # monitor incoming products
    exec("$bin_path/pqutil -f $feedset -w $pq_path");
}

The headers on NOAAPORT products in the IDD should never have NULLs in
them.  What feed are you looking at?  Have you discussed this situation
with whoever created the feed?

The other option you can explore is the use of the LDM utility, notifyme.

>Also, it is a bit annoying that ldmadmin watch can't be put into the 
>background, because it is trying to read from the terminal.

>Attempting to run
>$ ldmadmin watch >& /tmp/lw.out &
>$ jobs
>
>results in
>  Suspended (tty output)        ldmadmin watch >& /tmp/lw.out

Try running pqutil directly instead of running ldmadmin.

Tom Yoksas