1just-man-pages/condor_vacate(G1e)neral Commands Manjuuaslt-man-pages/condor_vacate(1)
2
3
4

Name

6       condor_vacate Vacate jobs that are running on the specified hosts
7

Synopsis

9       condor_vacate [ -help -version ]
10
11       condor_vacate  [  -graceful  -fast ] [ -debug ] [ -pool centralmanager‐
12       hostname[:portnumber] -name name ][ -addr <a.b.c.d:port> ] ...  [  -all
13       ]
14

Description

16       condor_vacate  causes Condor to checkpoint any running jobs on a set of
17       machines and force the jobs to vacate the machine. The  job(s)  remains
18       in the submitting machine's job queue.
19
20       Given  the (default) -graceful option, a job running under the standard
21       universe will first produce a checkpoint  and  then  the  job  will  be
22       killed.  Condor  will  then  restart  the job somewhere else, using the
23       checkpoint to continue from where it left off. A job running under  the
24       vanilla universe is killed, and Condor restarts the job from the begin‐
25       ning somewhere else.  condor_vacate has no effect on a machine with  no
26       Condor job currently running.
27
28       There  is generally no need for the user or administrator to explicitly
29       run condor_vacate . Condor takes care of jobs in this way automatically
30       following the policies given in configuration files.
31

Options

33       -help
34
35          Display usage information
36
37
38
39       -version
40
41          Display version information
42
43
44
45       -graceful
46
47          Inform the job to checkpoint, then soft-kill it.
48
49
50
51       -fast
52
53          Hard-kill jobs instead of checkpointing them
54
55
56
57       -debug
58
59          Causes  debugging  information  to  be  sent to stderr, based on the
60          value of the configuration variable TOOL_DEBUG
61
62
63
64       -pool centralmanagerhostname[:portnumber]
65
66          Specify a pool by giving the central  manager's  host  name  and  an
67          optional port number
68
69
70
71       -name name
72
73          Send the command to a machine identified by name
74
75
76
77       name
78
79          Send the command to a machine identified by name
80
81
82
83       -addr <a.b.c.d:port>
84
85          Send the command to a machine's master located at <a.b.c.d:port>
86
87
88
89       <a.b.c.d:port>
90
91          Send the command to a machine located at <a.b.c.d:port>
92
93
94
95       -all
96
97          Send the command to all machines in the pool
98
99
100

Exit Status

102       condor_vacate  will  exit with a status value of 0 (zero) upon success,
103       and it will exit with the value 1 (one) upon failure.
104

Examples

106       To send a condor_vacate command to two named machines:
107
108       % condor_vacate  robin cardinal
109
110       To send the condor_vacate  command  to  a  machine  within  a  pool  of
111       machines  other than the local pool, use the -pool option. The argument
112       is the name of the central manager for the pool. Note that one or  more
113       machines  within the pool must be specified as the targets for the com‐
114       mand. This command sends the command to  a  the  single  machine  named
115       cae17  within  the pool of machines that has condor.cae.wisc.edu as its
116       central manager:
117
118       % condor_vacate -pool condor.cae.wisc.edu -name cae17
119

Author

121       Condor Team, University of Wisconsin-Madison
122

124       Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
125       versity   of  Wisconsin-Madison,  Madison,  WI.  All  Rights  Reserved.
126       Licensed under the Apache License, Version 2.0.
127
128       See  the  Condor  Version   7.4.2   Manual   or   http://www.condorpro‐
129       ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
130
131
132
133                                     date      just-man-pages/condor_vacate(1)
Impressum