Mailing List Archives

Public Access

 		[Computer Systems Lab]

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

Re: [HTCondor-users] Windows Keyboard Idle Isn't Working on 8.3.6

Todd,

Thank you very much for your help, that worked.

On 08/04/2015 06:03 PM, Todd Tannenbaum wrote:

On 7/31/2015 10:11 AM, Bud wrote:

condor_status KeyboardIdle attribute returns the right values - low when
I just moved the mouse and high when I left it alone for a while.

However, the jobs are started in those slots even when KeyboardIdle is,
say, 19 seconds, and are not stopped (all cores continuing to run job at
100%) when I move the mouse and reduce KeyboardIdle to 1.

Todd, may I ask what your working config file looks like compared to mine?
My condor_config file created by the installer looks like this (domain
and ips removed by me):
RELEASE_DIR = C:\condor
LOCAL_CONFIG_FILE = $(LOCAL_DIR)\condor_config.local
REQUIRE_LOCAL_CONFIG_FILE = FALSE
LOCAL_CONFIG_DIR = $(LOCAL_DIR)\config
use SECURITY : HOST_BASED
CONDOR_HOST = 0.0.0.0
UID_DOMAIN = mydomain.ca
CONDOR_ADMIN =
SMTP_SERVER =
ALLOW_READ = *
ALLOW_WRITE = $(CONDOR_HOST), *.mydomain.ca
ALLOW_ADMINISTRATOR = 0.0.0.0
JAVA = C:\PROGRA~2\Java\JRE18~1.0_4\bin\java.exe
DAEMON_LIST = MASTER STARTD KBDD

condor_config.local is empty. $(LOCAL_DIR)\config doesn't exist.


Hi Bud,

Try appending the following to your condor_config file if you only care about keyboard activity

   use policy : Desktop
   START = (KeyboardIdle > 15 * 60)

Or if you want to also avoid starting jobs if the cpu is busy (i.e. avoid desktops if the owner started a cpu intensive foreground job and then went home), try appending something like

   use policy : Desktop
   START = ( (KeyboardIdle > 15 * 60) && \
    ( ((LoadAvg - CondorLoadAvg) <= 0.3) || \
    (State != "Unclaimed" && State != "Owner")) )

The addition of START statement above is because that is missing due to a bug in the meta-knob definition of "use policy: Desktop" - we are fixing that one this week, you can see the bug ticket at https://goo.gl/zTZByf. Also we are investigating a possible regression bug in the Windows MSI installer, since you shouldn't have to append things to the config by hand after running the installer - bug ticket at https://goo.gl/rlHuh3.  Thank you for bringing these to our attention.

If you want to see specifically what the policy metaknobs do you can use condor_config_val like so (note a definition for START is missing):

C:\home>condor_config_val use policy:desktop
use POLICY:DESKTOP is
         WANT_SUSPEND=($(SmallJob) || $(KeyboardNotBusy) || $(IsVanilla) ) && ( $(SUSPEND))
         WANT_VACATE=$(ActivationTimer) > 600 || $(IsVanilla)
         SUSPEND=($(KeyboardBusy) || ( (CpuBusyTime > 120) && $(ActivationTimer) > 90))
         CONTINUE=($(CPUIdle) && ($(ActivityTimer) > 10) && (KeyboardIdle > $(ContinueIdleTime)))
         PREEMPT=(((Activity == "Suspended") && ($(ActivityTimer) > $(MaxSuspendTime))) || (SUSPEND && (WANT_SUSPEND == False)))
         KILL=False
         MaxJobRetirementTime=0
         CLAIM_WORKLIFE=

Hope the above helps,
Todd


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/