[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] return of the KeyboardIdle bug ??
- Date: Wed, 5 May 2010 10:00:43 +0800
- From: <Greg.Hitchen@xxxxxxxx>
- Subject: Re: [Condor-users] return of the KeyboardIdle bug ??
Same here for 7.4.* Ian, we just added it to the DAEMON_LIST and
it all works OK.
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Smith, Ian
Sent: Tuesday, 4 May 2010 10:15 PM
To: 'Condor-Users Mail List'
Subject: Re: [Condor-users] return of the KeyboardIdle bug ??
Good news - I seem to have got this working but I'm not entirely sure how.
I went back to the beginning and just put KBDD in the DAEMON_LIST
and it seems to work - very strange !
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-
> bounces@xxxxxxxxxxx] On Behalf Of Todd Tannenbaum
> Sent: 29 April 2010 22:45
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] return of the KeyboardIdle bug ??
> Smith, Ian wrote:
> >> 3. Your registry tells Windows to run the condor_kbdd.exe upon login, aka
> >> "CONDOR_KBDD"="c:\\condor\\bin\\condor_kbdd.exe"
> > OK this was missing after the MSI install so I put it in myself and logged out and
> Ok, I will look into the above...
> >> Troubleshooting questions:
> >> - When you login, does the task manager show the condor_kbdd running?
> > It does now after the regedit.
> >> - With STARTD_DEUBG = D_COMMAND, do you see the "command_x_event"
> >> entries similar to the following in the StartLog when using the console
> >> of the machine?
> >>> 04/26 10:06:44 Received UDP command 427 (X_EVENT_NOTIFICATION) from
> >>> <xx.xx.xx.xx:1392>, access level ALLOW
> > Nope not with D_COMMAND and not even anything remotely like this with
> This is a problem, and puzzling. (after setting STARTD_DEBUG =
> D_COMMAND I assume you did a condor_reconfig).
> Lets see what the kbdd thinks it is doing... Could you change the
> config entry for KBDD_LOG from c:\NUL to be instead a local file that is
> world writable (i.e. somewhere any user can write), add "KBDD_DEBUG =
> D_ALL", logout and log back in (to get a new condor_kbdd instance), and
> finally pass along the resulting kbdd log file to me? The kbdd should
> be contacting the startd every ~5 seconds or so when it sees mouse or
> keyboard activity.
> Another data point - it should work either way, but is the keyboard a
> physical keyboard or are you coming in via remote desktop or some such?
> > I'm wondering about the "access level ALLOW" bit - perhaps I have the
> authorisation settings too
> > tight ? Surely I'd still see something in the log even if the authorisation policy
> blocked the update.
> The "access level ALLOW" bit is expected and desired in Condor v7.4.2.
> The idea is in earler versions folks were setting up authorization
> policies too tight, such that the startd was not accepting the message
> from the kbdd. In v7.4.2, the startd is hard-wired to always accept the
> X_EVENT_NOTIFICATION message from the kbdd to prevent against these
> sorts of configuration issues. To prevent against DoS attacks, however,
> the startd confirms that the message is coming from a local ip address.
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/condor-users/
> Todd Tannenbaum University of Wisconsin-Madison
> Center for High Throughput Computing Department of Computer Sciences
> tannenba@xxxxxxxxxxx 1210 W. Dayton St. Rm #4257
> Phone: (608) 263-7132 Madison, WI 53706-1685
> 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:
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: