Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #524
Difficulty: Medium
The ASCII table was designed to enforce a lexicographic ordering: letters are in alphabetic order, uppercase precede lowercase versions, and numbers come after both.
True or False?
Linux & Unix Commands - Search Man Pages

condor_convert_history(1) [debian man page]

condor_convert_history(1)				      General Commands Manual					 condor_convert_history(1)

Name
       condor_convert_history Convert - the history file to the new format

Synopsis
       condor_convert_history[-help]

       condor_convert_historyhistory-file1[history-file2...]

Description
       As  of  Condor  version 6.7.19, the Condor history file has a new format to allow fast searches backwards through the file. Not all queries
       can take advantage of the speed increase, but the ones that can are significantly faster.

       Entries placed in the history file after upgrade to Condor 6.7.19 will automatically be saved in the new format. The new format adds infor-
       mation  to  the	string which distinguishes and separates job entries. In order to search within this new format, no changes are necessary.
       However, to be able to search the entire history, the history file must be converted  to  the  updated  format.	condor_convert_historydoes
       this.

       Turn the condor_schedddaemon off while converting history files. Turn it back on after conversion is completed.

       Arguments  to  condor_convert_historyare  the  history  files to convert. The history file is normally in the Condor spool directory; it is
       named  history . Since the history file is rotated, there may be multiple history files, and all of them should be converted. On Unix plat-
       form variants, the easiest way to do this is:

       cd `condor_config_val SPOOL`
       condor_convert_history  history*

       condor_convert_historymakes  a  back  up  of each original history files in case of a problem. The names of these back up files are listed;
       names are formed by appending the suffix  .oldver to the original file name. Move these back up files to a directory other than	the  spool
       directory. If kept in the spool directory, condor_historywill find the back ups, and will appear to have duplicate jobs.

Exit Status
       condor_convert_historywill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

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_convert_history(1)

Check Out this Related Man Page

condor_master(1)					      General Commands Manual						  condor_master(1)

Name
       condor_master The - master Condor Daemon

Synopsis
       condor_master

Description
       This  daemon  is  responsible for keeping all the rest of the Condor daemons running on each machine in your pool. It spawns the other dae-
       mons, and periodically checks to see if there are new binaries installed for any of them. If there are, the condor_masterwill  restart  the
       affected  daemons.  In  addition,  if  any  daemon  crashes, the condor_masterwill send e-mail to the Condor Administrator of your pool and
       restart the daemon. The condor_masteralso supports various administrative  commands  that  let  you  start,  stop  or  reconfigure  daemons
       remotely. The condor_masterwill run on every machine in your Condor pool, regardless of what functions each machine are performing.

       Section 3.1.2in the Administrator's Manual has more information about the condor_masterand other Condor daemons. See Section 3.9.2for docu-
       mentation on command line arguments for condor_master.

       The  DAEMON_LIST configuration macro is used by the condor_masterto provide a per-machine list of daemons that should be started  and  kept
       running.  For  daemons that are specified in the  DC_DAEMON_LIST configuration macro, the condor_masterdaemon will spawn them automatically
       appending a -fargument. For those listed in  DAEMON_LIST , but not in  DC_DAEMON_LIST , there will be no -fargument.

Options
       -n name

	  Provides an alternate name for the condor_master to override that given by the  MASTER_NAME configuration variable.

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_master(1)

Featured Tech Videos