Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] do I have to use custom classad functions?
- Date: Fri, 29 Apr 2005 16:01:31 -0400
- From: <gregg.cooke@xxxxxxx>
- Subject: [Condor-users] do I have to use custom classad functions?
I've been playing around with job submission policies in my submit files and I have a few scenarios that I can't see a way around except by using custom classad functions:
- I'd like to submit a job that will only go to those machines that are also running some other application...for instance, a daemon whose service my task would use. The idea is to make a "service-sensitive" policy. I suppose I could do this by writing a classad function but I don't have access to the source code (yet).
- I'd like to submit a job that will only go to machines that have a certain shared filesystem mounted. Again, a classad function might work...but I don't think I can do that (...can I? or do I really need the source code to add my own functions?)
Both of these could be done if I had the ability to run a shell command and assign the output to an attribute in my machine classad. Is there a way to do this without getting the source code and writing a new classad function? Or has someone written a classad function that I can use to do this? Are there libraries of contributed functions out there that I might tap into?
-Gregg
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.