File: condor_urlfetch.rst

package info (click to toggle)
condor 23.9.6%2Bdfsg-2.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 60,012 kB
  • sloc: cpp: 528,272; perl: 87,066; python: 42,650; ansic: 29,558; sh: 11,271; javascript: 3,479; ada: 2,319; java: 619; makefile: 615; xml: 613; awk: 268; yacc: 78; fortran: 54; csh: 24
file content (64 lines) | stat: -rw-r--r-- 2,476 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
      

*condor_urlfetch*
==================

fetch configuration given a URL
:index:`condor_urlfetch<single: condor_urlfetch; HTCondor commands>`\ :index:`condor_urlfetch command`

Synopsis
--------

**condor_urlfetch** [**-<daemon>** ] *url* *local-url-cache-file*

Description
-----------

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:

.. code-block:: condor-config

    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 *local-url-cache-file*
does 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.

Options
-------

 **-<daemon>**
    The upper case name of the daemon issuing the request for the
    configuration output. If ``-MASTER``, then the URL query always
    occurs. If a daemon other than ``-MASTER``, for example ``STARTD``
    or ``SCHEDD``, then the URL query only occurs if the file defined by
    *local-url-cache-file* does not exist.

Exit Status
-----------

*condor_urlfetch* will exit with a status value of 0 (zero) upon
success and non zero otherwise.