Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
On Feb 14, 2013, at 5:37 AM, Harshad Prajapati <harshad.b.prajapati@xxxxxxxxx> wrote:On the execute machine, HTCondor creates a temporary directory for each job to run in. All files for the job are stored there while the job runs and the directory is deleted when the job completes. There are no configuration parameters to disable the cleanup of this directory.
> My question is related to submitting a job to condor using condor-g submission.
> I want to see where transferred executable and input files are stored on execute machine for job submitted using condor-g. Similarly, what about output file?
> Moreover, I want to keep those files on execute machines, what configuration do I need to do?
> Do I need to configure gsi-gatekeeper of globus or Startd of condor?
On the gatekeeper machine, Globus GRAM keeps job-related files in directories under the user's home directory. These directories are deleted when the GRAM client (e.g. Condor-G) tells it to do so.
Why do you want to keep these files on the execute machine after they've been transferred back to the job submitter?
Thanks and regards,
Jaime Frey
UW-Madison HTCondor Project
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/