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

NAME

6       condor_transfer_data - HTCondor Manual
7
8       transfer spooled data
9
10

SYNOPSIS

12       condor_transfer_data [-help | -version]
13
14       condor_transfer_data   [  -pool  centralmanagerhostname[:portnumber]  |
15       -name scheddname  ]  |  [-addr  "<a.b.c.d:port>"]  cluster...  |  clus‐
16       ter.process... | user... | -constraint expression ...
17
18       condor_transfer_data   [  -pool  centralmanagerhostname[:portnumber]  |
19       -name scheddname ] | [-addr "<a.b.c.d:port>"] -all
20

DESCRIPTION

22       condor_transfer_data causes HTCondor to transfer spooled  data.  It  is
23       meant  to  be used in conjunction with the -spool option of condor_sub‐
24       mit, as in
25
26          $ condor_submit -spool mysubmitfile
27
28       Submission of a job with the -spool option causes HTCondor to spool all
29       input  files,  the  job event log, and any proxy across a connection to
30       the machine where the condor_schedd daemon is running.  After  spooling
31       these files, the machine from which the job is submitted may disconnect
32       from the network or modify its local copies of the spooled files.
33
34       When the job finishes, the job has JobStatus = 4, meaning that the  job
35       has  completed.  The  output  of  the job is spooled, and condor_trans‐
36       fer_data retrieves the output of the completed job.
37

OPTIONS

39       -help  Display usage information
40
41       -version
42              Display version information
43
44       -pool centralmanagerhostname[:portnumber]
45              Specify a pool by giving the central manager's host name and  an
46              optional port number
47
48       -name scheddname
49              Send the command to a machine identified by scheddname
50
51       -addr "<a.b.c.d:port>"
52              Send the command to a machine located at "<a.b.c.d:port>"
53
54       cluster
55              Transfer spooled data belonging to the specified cluster
56
57       cluster.process
58              Transfer spooled data belonging to a specific job in the cluster
59
60       user   Transfer spooled data belonging to the specified user
61
62       -constraint expression
63              Transfer  spooled  data for jobs which match the job ClassAd ex‐
64              pression constraint
65
66       -all   Transfer all spooled data
67

EXIT STATUS

69       condor_transfer_data will exit with a status value  of  0  (zero)  upon
70       success, and it will exit with the value 1 (one) upon failure.
71

AUTHOR

73       HTCondor Team
74

76       1990-2023,  Center for High Throughput Computing, Computer Sciences De‐
77       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
78       under the Apache License, Version 2.0.
79
80
81
82
83                                 Oct 02, 2023          CONDOR_TRANSFER_DATA(1)
Impressum