Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
There is a technique we use sometimes for debugging jobs that hang waiting for a dialog box to be clicked.
If you shut down the Condor service, and then start up the condor_master interactively, it will do all of the things it normally does *except* allow jobs to run-as-owner. The jobs that HTCondor runs will have access to the desktop
of the user that ran the condor_master. Note that when you do this, all of the HTCondor daemons *and* the jobs will run as the user that started the condor_master. Any job that creates a window will create a visible one, and you will be able to see them and interact with them.
WARNING!! This also means that the jobs can do anything that the logged in user can do, so *donât* do this if you run jobs that are not trusted. If you need the process isolation that running HTCondor as a services gives you, you need to start the condor_master as the user LOCAL_SYSTEM which you cannot normally do outside of running it as a service.
But â there is a sysinternals tool that can start a command prompt as LOCAL_SYSTEM, and if you run the condor_master from that
you get all of the HTCondor capabilities, but will still have jobs creating visible windows.
-tj From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of don_vanchos Hello! The `USE_VISIBLE_DESKTOP = true` setting does not work on Windows 10, because the Interactive Services Detection Service has been removed in Windows 10 Version 1803 (released in April 2018). While applications running in Session 0 will
happily create windows and prompts, no one will be able to see them. Although it still works well on Windows 7. Is there another way to see the application window launched by the htcondor on Windows 10? -- Sincerely yours, |