Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
A
node being "Unclaimed" has nothing to do with keyboard/mouse activity. It is
merely unclaimed
in the context of Conod, i.e. no condor process (job) has claimed that
node in order to run a job.
You need to check the KeyboardIdle parameter in the machine
classad.
e.g. condor_status -l machinename | findstr
KeyboardIdle
This will show the number of seconds since the last keyboard/mouse
activity
A
machine can sometimes appear as Owner when the non-condor CPU load is high
enough
condor_status -l machinename | findstr Cpu
will show the Cpu related classads.
Have you tested a node by sending a job to it, then sitting at it and
moving/clicking the mouse
and/or keyboard and seeing if the job is evicted? (providing you have set
your configs that way).
Cheers
Greg
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Fabrice Bouye Sent: Wednesday, 1 June 2011 10:20 AM To: condor-users@xxxxxxxxxxx Subject: [Condor-users] [Condor 7.6.0] User activity detection woes under W7 & Vista Hi, We?ve had issues with condor 7.4.2 & 7.4.4 not detecting
correctly user activity on Windows 7 in the past but we tried to live with it
as, at that time, we had only a few computers with this OS in our pool and most
of the time their users were the ones wanting to run tasks on condor.
However this year, due to an increase of both newcomers and
replacement of old computers in our programme, we?ve reach the point where W7
computers make between 1/3 and 50% of all nodes in the pool. So condor loosing
the presence of the user and starting heavy tasks around is now a more pressing
issue than what it used to be. In order to try fix that, I?ve installed condor 7.6.0 on some
test PCs, made some quick fixes to our local config file and those nodes were
ready to fly. I?ve also had a look to the ?Upgrading from the 7.4 series to the
7.6 series of Condor? manual page (http://www.cs.wisc.edu/condor/manual/v7.6/8_2Upgrading_from.html)
and, as a consequence, I?ve added KBDD to the DAEMON_LIST variable in the local configuration
file for each testing node. I?ve
checked in the logs that kbdd starts OK and condor_kbdd.exe is reported by the
task manager as running. However, this does not seem to change anything as the
computer still listed as Unclaimed most of the time. Sometimes for unknown
reasons the computer is marked at Owner for 15min~1h before quickly going back
to unclaimed again. But most of the time it looks like my mouse & keyboard
activity just goes unnoticed. From what I?ve experienced on one of my test laptops, mouse
and keyboard activity detection on Windows Vista seems to be sketchy as
well. Are there any plans to fix finally this issue in a future
release? Or is there a working workaround available? Thanks. ----
|