[Swift-devel] Re: execute2 IDs
Mihael Hategan
hategan at mcs.anl.gov
Sat Sep 29 11:22:07 CDT 2007
On Sat, 2007-09-29 at 10:38 +0000, Ben Clifford wrote:
> execute2s used to have an explicit unique ID - the jobid; but not after
> r1268 was put it, it looks like, because that comes from the execute layer
> and is shared by all execute2 that run inside an execute.
>
> it looks like that will change the behaviour of job working directories -
> rather than having a separate job directory and kickstart record for each
> attempt to run (i.e. each execute2) I think that means that these will now
> attempt to be shared between all invocations.
>
> I think (at least from the kickstart perspective) that is undesirable.
Hmm. I did that because you seem to have wanted logging messages at the
execute level. Perhaps that should be reversed.
>
> It would be useful to have both an execute-level ID (roughly analogous to
> a VDL1 derivation name) and an execute2-level ID (that identifies a
> particular attempt to perform a VDL1-derivation-analogue).
I think that's too much complication. We'll stick with the thread as
being the execute level ID.
>
More information about the Swift-devel
mailing list