[Swift-devel] Use case and examples needed to avoid large directories

[Mihael Hategan]

On Tue, 2007-10-02 at 13:47 -0500, andrewj at uchicago.edu wrote:
>   First off, before I attempt to pose a further question I
> have, who is in the CI currently or regularly?

I usually get here around noon. My office has moved to the far west end
of the CI (near the AG node).

> 
> Thanks,
> Andrew   
> 
> 
> 
> ---- Original message ----
> >Date: Sat, 29 Sep 2007 08:42:59 +0000 (GMT)
> >From: Ben Clifford <benc at hawaga.org.uk>  
> >Subject: Re: [Swift-devel] Use case and examples needed to
> avoid large directories  
> >To: Michael Wilde <wilde at mcs.anl.gov>
> >Cc: swift-devel <swift-devel at ci.uchicago.edu>, Andrew
> Jamieson <andrewj at uchicago.edu>
> >
> >In brief, if you have a file in your submit directory called:
> >
> >  (swifthome)/a/b.txt
> >
> >and map it somehow:
> >
> > file f <"a/b.txt">;
> >
> >then on the submit side, in the run directory it will map to
> individual 
> >job execution directory like this:
> >
> >  (individualjobdir)/a/b.txt
> >
> >This should be the case for inputs, outputs and intermediates.
> >
> >If you want to map everything in the 'a' directory, you can
> map something 
> >like:
> >
> > file f[] <filesys_mapper; location="a">;
> >
> >to get an array containing every file in a.
> >
> >
> >Its meant to be the case that you can also store stuff
> elsewhere (on the 
> >same machine or on any gridftp server) rather than directly
> in the submit 
> >directory but I had some troubles when playing with it so I
> have a bug 
> >open and am waiting on that before further documentation of
> that bit.
> >
> >-- 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>