[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Pushing ClassAds into theenvironment forrunningjobs?



You can read about $$() expressions here:

http://www.cs.wisc.edu/condor/manual/v6.6/condor_submit.html#36286

In short, it should do precisely what you want. However, I've heard reports that $$ substitution got broken in the development series (6.7.0-6.7.2). This problem will be fixed in the next release. Sorry!

--Dan

Ian Chesal wrote:

When does $$(HOSTNAME) get expaned? When the job is submitted or when
the job begins to execute? Really what I'd like to do is know the vm#
for the job as well, which $$(HOSTNAME) won't give me but the RemoteHost
ClassAd from the job would.

Ian



-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Bryan S. Maher
Sent: November 3, 2004 3:30 PM
To: Condor-Users Mail List
Subject: RE: [Condor-users] Pushing ClassAds into the environment forrunningjobs?


Ian,

Perhaps I misunderstand but I think you can accomplish this by putting this in your submission file:

Environment = REMOTEHOST=$$(HOSTNAME)

-Bryan

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal
Sent: Wednesday, November 03, 2004 3:23 PM
To: Condor-Users Mail List
Subject: [Condor-users] Pushing ClassAds into the environment for runningjobs?


I can't see an obvious way to accomplish this: I'd to push some ClassAd values from the running machine and even the job into the enviroment for a job when it gets started. For example RemoteHost as environment variable REMOTEHOST so my job executable or script can read that environment variable and know more about itself. Is that possible?

The only option I can see right now is some how getting the script/executable running to figure out which machine classad and which job classad match to this job by looking at the hostname and the current working directory for the job and querying condor_status and condor_q with those constraints. Seems like a really round-about way to help a job learn all about itself once it starts running.

Ian

_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users



_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users




_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users