1CONDOR_URLFETCH(1)              HTCondor Manual             CONDOR_URLFETCH(1)
2
3
4

NAME

6       condor_urlfetch - HTCondor Manual
7
8       fetch configuration given a URL
9
10

SYNOPSIS

12       condor_urlfetch [-<daemon> ] url local-url-cache-file
13

DESCRIPTION

15       Depending  on the command line arguments, condor_urlfetch sends the re‐
16       sult of a query from the url to both standard  output  and  to  a  file
17       specified by local-url-cache-file, or it sends the contents of the file
18       specified by local-url-cache-file to standard output.
19
20       condor_urlfetch is intended to be used  as  the  program  to  run  when
21       defining configuration, such as in the nonfunctional example:
22
23          LOCAL_CONFIG_FILE = $(LIBEXEC)/condor_urlfetch -$(SUBSYSTEM) \
24            http://www.example.com/htcondor-baseconfig  local.config |
25
26       The pipe character (|) at the end of this definition of the location of
27       a configuration file changes the use of the definition. It  causes  the
28       command  listed  on the right hand side of this assignment statement to
29       be invoked, and standard output becomes the configuration. The value of
30       $(SUBSYSTEM)  becomes  the  daemon that caused this configuration to be
31       read. If $(SUBSYSTEM) evaluates to MASTER, then the  URL  query  always
32       occurs, and the result is sent to standard output as well as written to
33       the file specified by argument local-url-cache-file. When  $(SUBSYSTEM)
34       evaluates to a daemon other than MASTER, then the URL query only occurs
35       if the file specified by local-url-cache-file does not  exist.  If  the
36       file specified by local-url-cache-file does exist, then the contents of
37       this file is sent to standard output.
38
39       Note that if the configuration kept at the URL site changes, and recon‐
40       figuration  is  requested,  the -<daemon> argument needs to be -MASTER.
41       This is the only way to guarantee that there will be  a  query  of  the
42       changed  URL contents, such that they will make their way into the con‐
43       figuration.
44

OPTIONS

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

EXIT STATUS

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

AUTHOR

58       HTCondor Team
59

61       1990-2023,  Center for High Throughput Computing, Computer Sciences De‐
62       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
63       under the Apache License, Version 2.0.
64
65
66
67
68                                 Oct 02, 2023               CONDOR_URLFETCH(1)
Impressum