Provide a good way for runners on the device to save files

[GoogleCodeExporter]

The motivation behind this is to make Caliper saving via --xmlSave (but not 
uploading, I think) work more intuitively. It saves an XML file on the 
filesystem, but the local directory is usually deleted, so in a lot of cases 
the XML file will be deleted (unless a non-deleted folder is specifically 
specified). This could be greatly improved if we made something like a folder 
(like "/vogar-permanent") that is copied back to the host upon completion of 
vogar. The Caliper runner could then put stuff in this folder, and it could be 
copied back to the host for later use (with --xmlUpload for example).

Original issue reported on code.google.com by jsha...@google.com on 21 Jul 2010 at 2:00

[GoogleCodeExporter]

We now copy back xml files from the vogar temporary directory. This could be 
easily extended to other types of files as desired. (A "files to retrieve 
pattern" could even be made an argument. Currently it's just *.xml basically.)

Original comment by jsha...@google.com on 3 Aug 2010 at 7:26

• Changed state: Fixed

[GoogleCodeExporter]

Would it be better to just have a well known directory that all files are 
uploaded from? That way I could use it with strace for example and tcpdump for 
example, by just arranging them to put the output in the well known dir.

Original comment by b...@google.com on 3 Aug 2010 at 8:11

[GoogleCodeExporter]

Hm, my trouble with that was that Caliper, for instance, shouldn't know about 
vogar at all, and it writes out some files automatically in failure cases, so I 
felt there was no opportunity for Vogar to force Caliper to use a particular 
directory.

But now that you mention it, I could just add an option to Caliper that gives 
it a working directory to put files in (and Vogar could set it to 
"vogar-permanent" or something).

The problem there is when you have arbitrary Main programs running that want to 
have files saved - how would they know where to put them?

Maybe it's best to allow the user to specify patterns during Vogar's invocation 
for the types of files they want to be slurped. That way, if you know a program 
is going to produce .xml files, you can get those, or if you know it's going to 
produce .tcpdump (or whatever) files, you can get those instead.

Original comment by jsha...@google.com on 3 Aug 2010 at 8:44

[GoogleCodeExporter]

Original comment by jsha...@google.com on 3 Aug 2010 at 8:45

• Changed state: Started