[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Writing to HKEY_CURRENT_USER when running jobson Windows
- Date: Tue, 26 Jun 2007 13:46:15 -0500
- From: Ben Burnett <burnett@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Writing to HKEY_CURRENT_USER when running jobson Windows
This question has come up in the past, but modifications have never been
made. That said, we do have a meeting tomorrow afternoon, so I'll ask the
team what they think about the addition and see what they think about it.
If the answer is no, I think I may have some other alternatives for you.
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal
Sent: Monday, June 25, 2007 11:06 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] Writing to HKEY_CURRENT_USER when running jobson
Ben, thanks for the response.
> You are correct in that Condor can run under specific accounts;
> currently, Condor does not load profiles for these accounts. What
> means is that the HKEY_CURRENT_USER is also not loaded, which is why
> you're writes have been failing.
Any chance this could be an optional decision? So if I wanted the
profile loaded by Condor I could ask for it? Could you wipe the profile
after the job completed as well so it always started clean for the next
> As an alternative to granting full administrative permissions to the
> Condor user, you might consider adding a new sub-key to the
> "HKEY_LOCAL_MACHINE\SOFTWARE\Condor" key (or a place of your choice).
> Then, using regedit (or regedt32 on Win2K/XP--MS seems to have finally
> integrated them into one in Vista) set the registry key's access
> permissions such that the Condor user can have the access to it you
> wanted (by right clicking on it and selecting "Permissions..."--this
> can also be done remotely and can also be automated, in case you have
> more machines that you care to do by hand). Finally, you can use
> the scheduler to remove the data once it is not needed (via some
> expire date key, or the like).
Thanks for the idea. I'll see what I can do to this end. Part of the
problem is Cygwin is involved here -- a custom version of Cygwin that we
ship with our CAD tool that includes a modified gcc that can produce
code for our soft core IP. It's all terribly complicated. Cygwin really
wants to write mount points to both HKEY_LOCAL_MACHINE and
HKEY_CURRENT_USER. It's a shame it can't be told to use some file-based
registry mimic when it's running in a restricted account.
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: