[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users] condor on windows server 2003
- Date: Thu, 2 Dec 2004 12:44:21 -0500
- From: "Bryan S. Maher" <Bryan.Maher@xxxxxxxxxx>
- Subject: RE: [Condor-users] condor on windows server 2003
Good idea. I only became aware of the VM1_USER trick through a
conversation with Colin in regards to the same permissions problem
Oliver was experiencing.
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of matthew hope
Sent: Thursday, December 02, 2004 12:12 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] condor on windows server 2003
might I suggest an entry in
concerning how to go about using a domain based rather than local user
(along with comments reflecting issues with SMP and execute login is
dedicated and how to work round it with multiple users)
Questions such as
How do you store the credentials?
What access rights should the domain user have on the local machine?
What versions this is possible from?
Security considerations? (moot point given that this will almost
certainly be used in the context of a closed fully trusted environment
but worth noting)
What happens if the domain controller hiccups/timesout etc etc...
On Thu, 02 Dec 2004 11:02:44 -0600, Colin Stolley <stolley@xxxxxxxxxxx>
> >I have the following in my condor_config file:
> > VM1_USER = MYDOMAIN\CONDOR
> > EXECUTE_LOGIN_IS_DEDICATED = TRUE
> >According to Collin, making the login dedicated allows condor to
assume all processes in that user context belong to the job and can be
> > By consequence, jobs vacated by VM1 would kill jobs run by VM2.
> Not exactly. VM1_USER is defined as MYDOMAIN\CONDOR, but VM2 is
> undefined, meaning it will use condor-reuse-vm2. If you said,
> VM2_USER = MYDOMAIN\CONDOR
> then Condor would behave as you described.
> Condor-users mailing list
Condor-users mailing list