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 Maggie, That would require changing the source code of ldmadmin. So, yes it is "possible" but it would require much work, something I do not see on our near horizon. However, many improvements are being made to the LDM currently, this unfortunatley is not currently one of the changes. However, some of our improvements will improve latency issues, but this is no solice for the poorly connected. I had mentioned a possible work-around for dropped products from these "poorly connected" sites to Teresa. It involves running a second LDM ingest machine that you could fire up and request the specific site that was dropping data and increase your -m (max latency) and -o (max offset) flags for the relevant (data dropped) time period. Unfortunately that is all I can currently offer, unless I am misunderstanding the problem. Thank you, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Fri, 15 Nov 2002, Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden, > >To: Teresa Van Hove <address@hidden> > >From: Maggie Sleziak <address@hidden> > >Subject: Settings for ldm to not time out quickly > >Organization: UCAR > >Keywords: 200211151739.gAFHdYL07750 > > Hello, > > I was wondering if you could suggest any settings that might help ldm > not time out so quickly with one of our sites SC01 (ip#129.138.88.80) > > We did get a couple of files form SC01 cpu, so we don't think that it is > a permissions issue, but a slow connection problem. > > Thank you very much > > Best Regards, > Maggie > > Example of ldmd.log > > Nov 11 01:55:00 suomildm2 129.138.88.80[29098]: FEEDME(129.138.88.80): > h_clnt_create(129.138.88.80): Timed out while creating connection > > Nov 11 02:08:10 suomildm2 129.138.88.80[29098]: FEEDME(129.138.88.80): > h_clnt_create(129.138.88.80): Timed out while creating connection > > > > > -- > Maggie Sleziak > Programmer Tech > GST Cosmic UCAR/NCAR > address@hidden > > > ------- End of Forwarded Message > >