[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] The system cannot find the drive specified.
- Date: Tue, 18 Nov 2008 15:57:27 -0500
- From: "Alas, Alex [FEDI]" <aalas@xxxxxxxxxxxxx>
- Subject: Re: [Condor-users] The system cannot find the drive specified.
I understand the lean initial environments on condor and that is why I
set up the cred_host configuration on the same box is running as Central
manager. I am sorry If I didn't stated in my initial e-mail, like I said
in other post message I am new in Condor and still getting use to the
technology itself. I actually accommodate my condor farm to get
authenticated through the network shares using Method D (Create and Have
Condor Use a special account) from the section 6.26 of the Condor
Manual. I had also configured all the execute/submit machines with the
necessary to steps to modify their condor_config files to run as that
special users account. I added the condor_pool password and that
condoruser special credentials on each machine by using the
condor_store_cred command. I don't know is this change what you stated
before but to get the best help I think that piece of information needs
to be known.
Thanks again for your help,
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal
Sent: Tuesday, November 18, 2008 2:15 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] The system cannot find the drive specified.
A few things are useful to know when running jobs on Windows via Condor:
1. Condor runs your jobs in really lean initial environments. It does
not mount Windows drives for your job.
Not a hard problem to overcome. Just make the first set of commands in
your jobs the necessary "net use" calls you need to setup your drives.
The tricky part is what to do if your shares require authentication to
mount. You've got a few ways to approach this. The easiest, least
secure: always do your mounts as one domain account and put the password
in plaintext in your job script.
2. If you're not using the credential daemon your jobs run as limited
local user accounts. These accounts generally don't have access to
shares that require domain-level authentication.
Ties in to #1 and how you do authentication to remote shares. If you can
stomach the security hole try running the shares you need as completely
open shares, no authentication required. Samba works well for setting up
these kinds of shares.
3. Each job on Windows runs in its own virtual desktop space (unless
you're using USE_VISIBLE_DESKTOP, which you shouldn't).
This means jobs don't share mounts. So every job can do drive mounts as
if it's the only job on the machine.
> Where, \\FILESERVER\sharename are the same path in
Transfer_input_files and Executable.
This'll only work if \\FILESERVER\sharename doesn't require your job to
authenticate. See my comment about limited local user accounts. You're
not using Condor credd daemon, right?
> TRANSFER_INPUT_FILES =
> EXECUTABLE = Y:\4Alex\lasEnvelop.bat
This won't work because Condor doesn't make the Y: drive mount for you.
I'd say put your time and energy in to make UNC (\\FILESERVER\sharename)
work instead of drive letter. It's the more flexible approach.
Hope that helps.
This message may contain information that is confidential or otherwise
protected from disclosure. If you are not the intended recipient, you
are hereby notified that any use, disclosure, dissemination,
distribution, or copying of this message, or any attachments, is
strictly prohibited. If you have received this message in error, please
advise the sender by reply e-mail, and delete the message and any
attachments. Thank you.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
You can also unsubscribe by visiting
The archives can be found at: