Re: [HTCondor-users] HTCondor "executable" DOS batch file - while jobs in the queue can the batch file be changed?

[Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>]

The former and current manual implies that copy_to_spool handles the executable, as opposed to an input sandbox, hence my mild Rube Goldbergisms.

If copy_to_spool is equivalent to the -spool command line option which mentions input files, event log, and proxy, then the docs should be updated a bit.

Or do we need both in order to get the executable, input files, event log, and proxy?

	-Michael Pelletier.

-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Greg Thain
Sent: Tuesday, April 3, 2018 11:55 AM
To: htcondor-users@xxxxxxxxxxx
Subject: [External] Re: [HTCondor-users] HTCondor "executable" DOS batch file - while jobs in the queue can the batch file be changed?

On 04/03/2018 10:19 AM, Michael Pelletier wrote:
> The executable and input transfers are grabbed at job startup. This has posed a bit of a problem in some of our cases with JAR files and input data when the users are actively building multiple scenarios with hours worth of Monte Carlos each.

The condor_submit -spool option, or the submit file directive "copy_to_spool" can direct condor to copy input sandbox or just the executable to the condor spool directory at submit time, if you don't want the default behavior.

-greg
_______________________________________________
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/