We need to run condor jobs in remote machines using run_as_owner..
Both the remote user and the user of the machine where the job is executed are in the same domain.
When we monitor the access to the registry done by the job, if we run the job as a local user, it accesses the registry key HKU\xxx where xxx is the registry hive for the local user.
However, when the job is run by a remote user, it will try to access the registry key for the remote user HKU\yyy which does not exist, and thus causes the job failure
This could be fixed by using load_profile, but in the documentation, it is mentioned that both features are currently not compatible
Isn’t there a workaround to solve this issue?
Almansour Belleh Blanco
R&D Automatic Segmentation
T +49 89 99 15 68 – 0
F +49 89 99 15 68 – 33
Kapellenstr. 12, 85622 Feldkirchen, Germany
Sitz d. Gesellschaft: Feldkirchen b. München - Handelsregister: München HRB 135 401
Vorstand: Stefan Vilsmeier (Vorsitz), Rainer Birkenbach, Joseph Doyle, Christoph Pedain – Vorsitzender d.
Aufsichtsrates: Dietrich von Buttlar
WEEE – Reg. – Nr. DE: 15147063
This email, including its attachments, is intended only for the confidential use of the individual to whom it is
addressed. If you are not the intended recipient, any use, dissemination, distribution or copying of this message
or its attachments is prohibited. If you have received this message in error, please notify us immediately, and
delete this message and its attachments permanently from your system.