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

[LDM #YEV-796822]: pqinserting a file from a non-ldm server

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: [LDM #YEV-796822]: pqinserting a file from a non-ldm server
  • Date: Wed, 03 Jan 2018 13:56:21 -0700
Greg,

pqinsert(1) copies *local* files into a *local* LDM product-queue.

The LDM utility ldmsend(1), on the other hand, sends local files to a *remote* 
LDM server. The remote LDM must have an ACCEPT entry for the host executing the 
ldmsend(1).

I hope this helps.

> I have a question about the nature of what pqinsert does. Here at my
> lab I have a data file that arrives on one server that I want to share with
> an outside user via ldm. I have a script set up to perform an: ssh -l ldm
> aeolus pqinsert -v -f EXP $path from the non-ldm server. Authentications
> have been taken care of and the command will run as part of the script. My
> question is does the file to be inserted ($path) physically have to be
> reachable on the ldm machine for this to work or does pqinsert itself
> transfer the contents of the file to the product-queue?


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YEV-796822
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.