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

Re: [Condor-users] KeyBoard Idle Time infinite

Steve Wilson in Biology here at Purdue came up with a neat trick.:

"I wrote a short program (condor_usb_fix) to monitor USB activity (/ dev/input/mice, in my case) and then update the access time on another file ( I use /dev/condor_mouse). I changed Condor's configuration to include this new "device file" (condor_mouse):
CONSOLE_DEVICES = mouse, console, condor_mouse
Then I added lines to start and stop my daemon from the Condor init script."

The code snip is at

I don't use it personally (don't run any the desktop Condor systems) but Steve does, and this seems to do the trick in his environment.

Steve, please chime in if I've misspoke anywhere..


On Feb 11, 2008, at 1:19 PM, Todd Tannenbaum wrote:

Saurabh Agarwal wrote:
Hello everybody.

I just checked my Condor StartLog and to my surprise I get this message
there which assumes infinite idle time for my mouse/keyboard stating:
"2/11 07:36:56 Unable to calculate keyboard/mouse idle time due to them
both being USB or not present, assuming infinite idle time for these

Does anyone have any idea, why is it so? and how can I configure my
condor to take in to account this measure,. I am sure the keyboard and
mouse are present and yes they are connected through USB, so how do I
make those changes to get such information. I mean I would like to know
the information when are the users coming back to the machine, and
"KeyboardIdle" will be the best ClassAd to give me such information.
I have installed Condor v 6.8.6 on my 3 machines, with one being the
Central Manager.

Condor does not know when there is activity on a USB connected keyboard
because the Linux kernel will not tell it.

IIRC, you have a couple options.  The most straight-forward is change
the kernel via a small patch as discussed here:
Over time many folks have requested many times for this patch to be
adopted into the mainline kernel, but so far it has not happened.

Another possibility is to use the condor_kbdd if you are always running an X server on your machine(s). The condor_kbdd monitors keyboard/ mouse
activity by asking the X server instead of the kernel, and it fowards
along what it discovers to the condor_startd.

Anyone aware of any alternatives beyond the two above?


Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Preston Smith  <psmith@xxxxxxxxxx>
Systems Research Engineer
Rosen Center for Advanced Computing, Purdue University