[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Not fully able to start jobs - permissions?

On May 16, 2005, at 12:08 PM, Rob Pieké wrote:

The starter on your execute machine is trying to open files in the spool directory of your submit machine. I'm guessing your pool is configured to have a shared filesystem and you submitted the job with the -r or -s argument to condor_submit.

Yes, you're right! We're using '-r' the way that we were in Condor 6.2. Comparing notes with others, it looks like we should be using '-n' to get the same results as we were before. Initial testing shows this seems to be working.

Can you elaborate a bit on '-r' vs '-n'?

Both -n and -r allow you to submit to a schedd other than the default one. -n assumes that all of the job's files are sitting on a filesystem accessible to the schedd (i.e. the schedd is on the local machine or all the job's files are on a share filesystem). -r assumes the schedd doesn't have direct access to the job's files, so condor_submit transfers them to the schedd. The job's output files are stored at the schedd and must be retrieved with condor_transfer_data. -r is identical to using both -n and -s.

|            Jaime Frey            |  Public Split on Whether        |
|        jfrey@xxxxxxxxxxx         |  Bush Is a Divider              |
|  http://www.cs.wisc.edu/~jfrey/  |         -- CNN Scrolling Banner |