NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
From what I can tell, its designed to minimize product delivery delays at the expense of bandwidth. A perfectly good application, but not ideal for our specific application since it’s not tuneable. In the end, I made two ldmd.conf files, one with a REQUEST line for our alternate site and one without. I have a cron job that runs every minute, checks the origin of the products in the queue for the last 30 seconds, and if there are none with an origin of my local NOAAPORT server, it switches out the ldmd.conf to the one with the alternate, and restarts LDM. If it’s running with the alternate config and the cron job sees that products are being inserted locally again, it switches back to the primary ldmd.conf that doesn’t have the REQUEST line from our remote source. From: Patrick L. Francis [mailto:wxprofessor@xxxxxxxxx] Sent: Monday, January 15, 2018 10:46 AM To: Greg Trotter <gtrotter@xxxxxxxxxx>; Karen Cooper - NOAA Affiliate <karen.cooper@xxxxxxxx> Cc: ldm-users@xxxxxxxxxxxxxxxx Subject: Re[2]: [ldm-users] question about primary and secondary data transfer Steve pointed me in a direction of some code to modify, I will see if that can do what I need. I agree, what you describe would be a very useful feature. It would be nice if you could select a preferred source and a secondary source that you only go to if your preferred source goes down for a specified amount of time. Wasn't that how it was originally? We had primary and secondary, and I assumed it only switched when needed, but then I'm not sure...
ldm-users archives: