[Swift-devel] Re: Problems with file and sfs stagingMethods

Mihael Hategan hategan at mcs.anl.gov
Mon Sep 27 16:29:30 CDT 2010


On Mon, 2010-09-27 at 14:45 -0600, wilde at mcs.anl.gov wrote:
> ----- "Mihael Hategan" <hategan at mcs.anl.gov> wrote:
> 
> ...
> > > > Essentially all staging paths need to now be of one of the
> > following
> > > > forms:
> > > > 1. <protocol>://<host>/<path>
> > > > 2. <protocol>:<path>
> > > > 3. <path>
> > > >
> > > > Also, direct providers (i.e. "sfs") need to have absolute paths
> > for
> > > > client files because the CWD of the client is unknown to the
> > worker.
> 
> By this sfs restriction do you mean that the Swift script needs to map files to absolute pathnames?

The worker needs an absolute location. But that was what the change was
about: transform a relative location received from swift/client into an
absolute location.

So no. You can now say file f <"relativepath">; in swift with sfs.

> 
> Does wrapper.invocation.mode=absolute also need to be set in swift.properties?

No.





More information about the Swift-devel mailing list