10-09-2005
The Red Team
To add to this. The first DARPA Grand Challenge was held a little more than 18 months ago. At that time no one completed the race. CMU's Sandstorm went about 7 miles and then crashed out of the challenge. None of the others even came up to 7 miles.
I was working under one of the CMU Prof's who also happened to be one of the external technical advisor for Sandstorm. The reason he gave for the crash was the technical people behind Sandstorm did not forsee the following situation: Encounter a curved uphill slope.
So apparently Sandstorm did not reduce its speed when it encountered the curved uphill slope. Hence it jumped the tracks, which lead it to crash and eventually one of the wheels caught fire.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to get my up arrow key to recall my previous commands in Korn shell.
Anyone help please?
thanks a bunch!
BG (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. UNIX for Dummies Questions & Answers
Hello every body,
Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris??
To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time.
FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies
3. UNIX for Advanced & Expert Users
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies
5. UNIX for Dummies Questions & Answers
Hello All,
Many developers in our company use same application account to log in Linux Box for code development, how can i redirect my log in shell history to a different file to avoid history being shown to others or accidentally execute the same command which i or others executed?
Thank you. (4 Replies)
Discussion started by: Ariean
4 Replies
6. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
LEARN ABOUT DEBIAN
condor_convert_history
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)