[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE : [Condor-users] pb of job submission on windows machine
- Date: Fri, 4 Mar 2005 09:30:44 +0100
- From: Régis Baudu <Regis.Baudu@xxxxxxxxxxxxx>
- Subject: RE : [Condor-users] pb of job submission on windows machine
In fact, I just want the program, started by condor on the windows machine, accessed files which are on a mounted drive (using samba).
The condor daemons and the program executes locally on the windows machine, let's say c: drive; and the program read and write on a linux filesystem I have previously mounted using samba (net use w: \\mylinuxmachine\tmpcondor).
When I try with the condor service started under 'local system', I get an error of the form: 'w:\test\mytest.txt : No such file or directory' and the file is there.
When I try with the condor service started under a windows local administrator account 'condor', I get the CreateProcessAsUser error.
So I do not think 'null session' is a solution in this case. I will try with the privileges but I think my problem is much more related to samba/windows configuration.
Thanks for your help.
De : condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] De la part de Colin Stolley
Envoyé : jeudi 3 mars 2005 23:28
À : Condor-Users Mail List
Objet : Re: [Condor-users] pb of job submission on windows machine
I guess I'd like to know why your condor daemons themselves need access
to the network. The jobs themselves run as a separate user, which can
access network resources when it has the appropriate credentials.
If you're attempting to keep the daemon log files on a network volume, I
would discourage it due to complications that can arise with file
locking (among other things).
If you're attempting to keep the daemon binaries on a network volume,
you can use null-sessions to accomplish this. Null sessions allow
unauthenticated users to access resources, which is unsafe, but
depending on your environment may not be the end of the world. See:
For more information.
As a last resort, if you insist on running your daemons as your 'Condor'
user, then you must make sure it has Administrator privileges. With
regards to the error you're seeing, the function that is failing is
actually CreateProcessAsUser(). According to Microsoft, the caller
should have SE_ASSIGNPRIMARYTOKEN_NAME and SE_INCREASE_QUOTA_NAME
privileges in order for it to complete successfully. Perhaps that is
what your 'Condor' user is missing.
Condor-users mailing list