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.
Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden > >cc: address@hidden > >From: Christopher Herbster <address@hidden> > >Subject: moving the ldm.pq file? > >Organization: Embry Riddle > >Keywords: 200203052023.g25KNYK17050 LDM ldm.pq > > I would like to move the ldm.pq file to a different filesystem. Can I do the > following: > > ldmadmin stop > > cp old_path/ldm.pq new_path/ldm.pq > > Make the appropriate change to the pq_path variable in ldmadmin > > ldmadmin start > > I'd prefer to do this so that we don't request those products that we already > have in the queue. > > I'd guess that this is okay to do, but I think that the pq file is "memory > mapped" and I want to make sure that this is only an issue when the ldm is > running. > > Thanks, as always, for the help! > > Chris H. > > ------- End of Forwarded Message -- Hi Chris, The process you described sounds fine. In theory you could probably cp the queue without stopping the ldm, but that might produce some odd results depending on exactly how cp works and what state the queue is in when the copy occurs. Better to have the queue in a known stable state. But, you mentioned copying the queue to another file system. Bear in mind that when the ldm is running the queue must be on a local disk. So, if you fire up the ldm using the new queue, that queue must be local. But, I don't fully understand your broader goal. Do you expect to do this often? Anne *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************