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

Re: [Condor-users] kbdd not working on windows server 2008



Doesn't the condor_kbdd send an update to the condor_startd every 5 seconds?
That's certainly what appears to be happening according to the StartLog file
(I have replaced some IP numbers with * 's):
 
07/25/11 10:01:15 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:15 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:15 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)
07/25/11 10:01:20 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:20 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:20 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)
07/25/11 10:01:25 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:25 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:25 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)
Running the command:
 
condor_status -l -direct machinename | findstr ConsoleIdle
 
continuously shows this as well as ConsoleIdle cycles from 0 up to 5 (0,1,2,3,4,5), then back
to 0 and cycles again, etc. when it is run from the computer "machinename".
 
Without the -direct option you are querying the Collector rather than machinename directly
so there can be a delay of up to UPDATE_INTERVAL (default 300s = 5 min).
However the startd will see activity and take the appropriate action (if any) quickly.
 
Cheers
 
Greg
 
 

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ziliang Guo
Sent: Monday, 25 July 2011 7:50 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] kbdd not working on windows server 2008

Uh, of course it doesn't if it's running like it does under XP.  If it's running under the Condor service in the system session, it can't see keyboard activity.  Which is why we've been trying to get it to run in the user session on user login.  Even when running under the user session, it can be up to 5 minutes before the startd is updated about keyboard/mouse activity.


--
Condor Project Windows Developer