Bug 615043 - Windows Documentation
Windows Documentation
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Grid_User_Guide (Show other bugs)
Development
All Windows
low Severity medium
: 1.3
: ---
Assigned To: Lana Brindley
Jeff Needle
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-15 16:12 EDT by Timothy St. Clair
Modified: 2013-10-23 19:17 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-14 16:10:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Timothy St. Clair 2010-07-15 16:12:52 EDT
We will want to pull in section 6.2 from the condor manual and prune some pieces, and elaborate on others.   

http://www.cs.wisc.edu/condor/manual/v7.4/6_2Microsoft_Windows.html
Comment 1 Lana Brindley 2010-07-15 22:27:26 EDT
This will be addressed in the next version of the document.

LKB
Comment 4 Lana Brindley 2010-08-05 19:23:10 EDT
Draft is now available on the stage for review. Based on:
https://docspace.corp.redhat.com/docs/DOC-44344

LKB
Comment 7 Timothy St. Clair 2010-09-08 16:37:12 EDT
Upon feedback from Matt, it may not be clear to the user that load_profile is run from the run account because the 1st mention is after that section.  

If you were to rearrange:  (Starting and stopping jobs under Microsoft Windows) b4 (Executing jobs with the user profile loaded) a linear read would have enough information for it to all make sense.  


I would also change: 

This error is resolved by giving explicit access to the submitting user's registry hive. Access can be allowed by using the load_profile command in the job's submit description file: 

To: 

This error is resolved by giving explicit access to the *run account* registry hive. Access can be allowed by using the load_profile command in the job's submit description file:

Note You need to log in before you can comment on or make changes to this bug.