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

Re: [Condor-users] 6.7.14 change in macros?



It's related to my other post, "Bug with TotalJobSuspendTime?"

Here's the classad code that continues the suspend from that post:

# continue on VM1 if keyboard not used,
# or VM2 becomes unused,
# or job has been suspended more than than max suspend time
CONTINUE	 = (KeyboardIdle > $(ContinueIdleTime)) \
		|| ( (vm2_Activity != "Busy") && (vm2_LoadAvg <
$(BackgroundLoad)) )

Prior to the above classad I define:
UPDATE_INTERVAL		= 3 * $(MINUTE)
ContinueIdleTime	= $(UPDATE_INTERVAL) / 2

This used to work w/o the $() around UPDATE_INTERVAL.  Now if I don't
use $(), I get an error in the StartLog:

1/19 12:46:31 Got SIGHUP.  Re-reading config files.
1/19 12:46:32 ERROR "Can't evaluate CONTINUE" at line 1086 in file
..\src\condor_startd.V6\Resource.C
1/19 12:46:32 vm1: Changing state and activity: Claimed/Suspended ->
Preempting/Killing
1/19 12:46:32 vm2: Changing state and activity: Claimed/Busy ->
Preempting/Killing
1/19 12:46:32 startd exiting because of fatal exception.

But with the $(), it works:

1/19 12:49:36 Got SIGHUP.  Re-reading config files.
1/19 12:54:47 vm1: State change: SUSPEND is TRUE
1/19 12:54:47 vm1: Changing activity: Busy -> Suspended
1/19 12:56:27 vm1: State change: CONTINUE is TRUE
1/19 13:00:03 vm1: Changing activity: Suspended -> Busy

Ralph Finch, P.E.
Dept. of Water Resources
Bay-Delta Office, Room 215-13
Sacramento, CA  95814
916-653-7552
rfinch@xxxxxxxxxxxx
 

> I'm not aware of any changes. Can you give a more complete example?