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

20030728: -o -m recovering data older than 1 hour

Hi Rodger,

Yes either a -o for time offset

or a -m for max latency could be used to achieve this goal.

Probably best to use the -m flag, as you know how old (far) you want to go
back.

Keep in mind the ldm needs to be started and stopped to have the changes
take effect.

Cheers,

Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

On Mon, 28 Jul 2003, Unidata Support wrote:

>
> ------- Forwarded Message
>
> >To: address@hidden
> >From: "Rodger R. Getz" <address@hidden>
> >Subject: LDM - Solaris 2.6 - recovering data older than 1 hour
> >Organization: UCAR/Unidata
> >Keywords: 200307282214.h6SMEYHt018920
>
> Institution: AWIS Weather Services, Inc.
Package Version: 5.2.2 (will be
> upgrading to latest soon!)
Operating System: Solaris 2.6 Hardware
>
Information: Sun Netra
Inquiry: We ingest a NOAAPort feed using the ldm.
> We maintain a queue of more than 3 hours in case of power outage (the
> machine has UPS and generator backup). This machine then feeds another
> machine (a Netra) running the ldm which does all the actual processing.
> I want to be able to process products that are several hours old after
> the Netra has been down for maintenance. Do I just stick a "-m 7200"
> onto rpc.ldmd to allow a two hour latency? Is there a better way? Thanks
> for your assistance!
>
>
>
>
> ------- End of Forwarded Message
>
>