condor_findhost(1) [debian man page]
condor_findhost(1) General Commands Manual condor_findhost(1) Name condor_findhost find - machine(s) in the pool that can be used with minimal impact on currently running Condor jobs and best meet any spec- ified constraints Synopsis condor_findhost [-help] [-m] [-n num] [-c c_expr] [-r r_expr] [-p centralmanagerhostname] Description condor_findhostsearches a Condor pool of machines for the best machine or machines that will have the minimum impact on running Condor jobs if the machine or machines are taken out of the pool. The search may be limited to the machine or machines that match a set of constraints and rank expression. condor_findhostreturns a fully-qualified domain name for each machine. The search is limited (constrained) to a specific set of machines using the -coption. The search can use the -roption for rank, the criterion used for selecting a machine or machines from the constrained list. Options -help Display usage information and exit -m Only search for entire machines. Slots within an entire machine are not considered. -n num Find and list up to nummachines that fulfill the specification. numis an integer greater than zero. -c c_expr Constrain the search to only consider machines that result from the evaluation of c_expr. c_expris a ClassAd expression. -r r_expr r_expris the rank expression evaluated to use as a basis for machine selection. r_expris a ClassAd expression. -p centralmanagerhostname Specify the pool to be searched by giving the central manager's host name. Without this option, the current pool is searched. General Remarks condor_findhostis used to locate a machine within a pool that can be taken out of the pool with the least disturbance of the pool. An administrator should set preemption requirements for the Condor pool. The expression (Interactive =?= TRUE ) will let condor_findhostknow that it can claim a machine even if Condor would not normally preempt a job running on that machine. Exit Status The exit status of condor_findhostis zero on success. If not able to identify as many machines as requested, it returns one more than the number of machines identified. For example, if 8 machines are requested, and condor_findhostonly locates 6, the exit status will be 7. If not able to locate any machines, or an error is encountered, condor_findhostwill return the value 1. Examples To find and list four machines, preferring those with the highest mips (on Drystone benchmark) rating: condor_findhost -n 4 -r "mips" To find and list 24 machines, considering only those where the kflops attribute is not defined: condor_findhost -n 24 -c "kflops=?=undefined" Author Condor Team, University of Wisconsin-Madison Copyright Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu September 2012 condor_findhost(1)
Check Out this Related Man Page
condor_reconfig(1) General Commands Manual condor_reconfig(1) Name condor_reconfig Reconfigure - Condor daemons Synopsis condor_reconfig [-help -version] condor_reconfig[-debug] [-pool centralmanagerhostname[:portnumber]] [-name hostnamehostname-addr "<a.b.c.d:port>""<a.b.c.d:port>"-con- straint expression-all] [-daemon daemonname] Description condor_reconfigreconfigures all of the Condor daemons in accordance with the current status of the Condor configuration file(s). Once reconfiguration is complete, the daemons will behave according to the policies stated in the configuration file(s). The main exception is with the DAEMON_LIST variable, which will only be updated if the condor_restartcommand is used. Other configuration variables that can only be changed if the Condor daemons are restarted are listed in section 3.3.1on page . In general, condor_reconfigshould be used when making changes to the configuration files, since it is faster and more efficient than restarting the daemons. The command condor_reconfigwith no arguments or with the -daemon masteroption will cause the reconfiguration of the condor_masterdaemon and all the child processes of the condor_master. For security purposes (authentication and authorization), this command requires an administrator's level of access. See section 3.6.1on page for further explanation. Options -help Display usage information -version Display version information -debug Causes debugging information to be sent to stderr , based on the value of the configuration variable TOOL_DEBUG -pool centralmanagerhostname[:portnumber] Specify a pool by giving the central manager's host name and an optional port number -name hostname Send the command to a machine identified by hostname hostname Send the command to a machine identified by hostname -addr <a.b.c.d:port> Send the command to a machine's master located at "<a.b.c.d:port>" <a.b.c.d:port> Send the command to a machine located at "<a.b.c.d:port>" -constraint expression Apply this command only to machines matching the given ClassAd expression -all Send the command to all machines in the pool -daemon daemonname Send the command to the named daemon. Without this option, the command is sent to the condor_masterdaemon. Exit Status condor_reconfigwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure. Examples To reconfigure the condor_masterand all its children on the local host: % condor_reconfig To reconfigure only the condor_startdon a named machine: % condor_reconfig -name bluejay -daemon startd To reconfigure a machine within a pool other than the local pool, use the -pooloption. The argument is the name of the central manager for the pool. Note that one or more machines within the pool must be specified as the targets for the command. This command reconfigures the single machine named cae17within the pool of machines that has condor.cae.wisc.eduas its central manager: % condor_reconfig -pool condor.cae.wisc.edu -name cae17 Author Condor Team, University of Wisconsin-Madison Copyright Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu September 2012 condor_reconfig(1)