There is a bug in the 7.6.0 condor_kbdd daemon -- on resume
the listen port of the condor_startd can change and often does. If the
listen port of the condor_startd daemon changes, existing condor_kbdd instances
silently starts to fail to send updates on keyboard and mouse activity
to the startd. In this case you'll see your policies that normally rely
on keyboard idle and mouse idle timers start to fail.
Todd just reminded me - There was a bug in all versions
of Condor prior to 7.6 where if you restarted condor while a user was logged
on, the KBDD would not restart and would not know how to talk to the restarted
Condor daemons, so it would cease to work until you logged off and back
on again.
So the matrix is:
For all versions of Condor before 7.4.4
Use the MSI installer and the KBDD will work until you restart
Condor then it will fail until you logoff and back on.
For Condor 7.4.4 until 7.6.0
Use the MSI installer _or_ add KBDD to the DAEMON_LIST and
KBDD will work until you restart (see above).
For Condor 7.6.0 and later
Use the MSI installer _or_ add KBDD to the DAEMON_LIST, there
are no known bugs with the KBDD
Just wondering if someone has a summary of
the status of the condor_kbdd daemon
with regards to working correctly for Win7.
What version/s of 7.4 and 7.6 correctly detect
keyboard activity on Win7, and what (if anything)
special needs to be done to config files
(or the registry) to allow it to work?
I have searched the user-list archives and
wiki but am finding it difficult to
dig out this information.
Thanks for any info/help.
Cheers
Greg
P.S. Our "installs" are not via
MSI installs but via extracting and copying
the zip file