From de48f60901cd7a7ef83f8b688113b1ba192ca821 Mon Sep 17 00:00:00 2001 From: Michael Hanke Date: Mon, 10 Jan 2011 12:11:14 -0500 Subject: [PATCH] Condor to Blend --- future/blends/condor | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 future/blends/condor diff --git a/future/blends/condor b/future/blends/condor new file mode 100644 index 0000000..5f1e6eb --- /dev/null +++ b/future/blends/condor @@ -0,0 +1,26 @@ +Source: condor +Tasks: debian-science/distributedcomputing +Homepage: http://www.cs.wisc.edu/condor +Responsible: NeuroDebian Team +Language: C++, Perl +Author: Condor Team +License: Apache-2.0 +WNPP: 233482 +Published-Title: Condor - A Hunter of Idle Workstations +Published-Authors: Michael Litzkow, Miron Livny, and Matt Mutka +Published-In: Proceedings of the 8th International Conference of Distributed Computing Systems, pp. 104-111 +Published-Year: 1988 +Registration: http://www.cs.wisc.edu/condor/downloads-v2/ +Pkg-Description: workload management system + Like other full-featured batch systems, Condor provides a job queueing + mechanism, scheduling policy, priority scheme, resource monitoring, and + resource management. Users submit their serial or parallel jobs to Condor, + Condor places them into a queue. It chooses when and where to run the jobs + based upon a policy, carefully monitors their progress, and ultimately + informs the user upon completion. + . + Unlike more traditional batch queueing system, Condor can also effectively + harness wasted CPU power from otherwise idle desktop workstations. Condor + does not require a shared file system across machines - if no shared file + system is available, Condor can transfer the job's data files on behalf of + the user. -- 2.39.5