Re: [Condor-users] possible bugs on Condor 6.7.2?

[Derek Wright <wright@xxxxxxxxxxx>]

On Thu, 11 Nov 2004 13:58:56 -0600  Derek Wright wrote:

> ok, numerous reports on this.  i guess i'm going to do some
> controlled experiments and make sure this feature is still working
> like we expect. ;) i'll report what i find as soon as i have some
> results.

ok, it's definitely still working.  i think you're just all confused
about how this feature really works.

when you use "ON_EXIT_OR_EVICT", the intermediary files do *NOT* get
transfered back into the directory where you submitted the job from.
instead, they're stored in the per-job subdirectory of spool i
mentioned in a previous message.  in case it's not obvious, the naming
convention of these per-job directories is as follows:

cluster<#>.proc<#>.subproc<#>

so, if the job you care about is job 735.0, the directory would be:

spool/cluster735.proc0.subproc0

if you submit a vanilla job that writes periodic output to a file, you
set "when_to_transfer_ouput = ON_EXIT_OR_EVICT" in your submit file,
vacate it, and inspect the spool directory, you'll see the files are
getting written there, no problem.

furthermore, if your test job opens this file to append data (instead
of truncating it), everything works exactly as you'd expect.  future
runs just append more data to the file.  you don't even have to worry
about putting the file in transfer_input_files, since condor is nice
enough to notice that if it transfered it back for you and you're in
ON_EXIT_OR_EVICT mode, it will transfer that automatically as input
the next time your job runs.

however, you'll only see these file back in the directory you
submitted them from when the job *finally* exits.  just because
they're not in your local directory doesn't mean they're not being
transfered or that ON_EXIT_OR_EVICT doesn't work.

probably the manual should be more clear to avoid this confusion.

-derek