Depending on the command line arguments,
condor_urlfetch sends the result of a query from the
url to both standard output and to a file specified by
local-url-cache-file , or it sends the contents of the file specified by
local-url-cache-file to standard output.
condor_urlfetch is intended to be used as the program to run when defining configuration, such as in the nonfunctional example:
LOCAL_CONFIG_FILE = $(LIBEXEC)/condor_urlfetch -$(SUBSYSTEM) \
http://www.example.com/htcondor-baseconfig local.config |
The pipe character (| ) at the end of this definition of the location of a configuration file changes the use of the definition. It causes the command listed on the right hand side of this assignment statement to be invoked, and standard output becomes the configuration. The value of $(SUBSYSTEM) becomes the daemon that caused this configuration to be read. If $(SUBSYSTEM) evaluates to MASTER , then the URL query always occurs, and the result is sent to standard output as well as written to the file specified by argument
local-url-cache-file . When $(SUBSYSTEM) evaluates to a daemon other than MASTER , then the URL query only occurs if the file specified by
not exist. If the file specified by
local-url-cache-file does exist, then the contents of this file is sent to standard output.
Note that if the configuration kept at the URL site changes, and reconfiguration is requested, the
-daemon argument needs to be -MASTER . This is the only way to guarantee that there will be a query of the changed URL contents, such that they will make their way into the configuration.