help with legacy application

Message boards : API : help with legacy application
Message board moderation

To post messages, you must log in.

AuthorMessage
ryeterrell

Send message
Joined: 25 Aug 09
Posts: 23
United States
Message 27508 - Posted: 21 Sep 2009, 2:13:55 UTC

Hi everyone,

I'm hosting a boinc project, and I use the "wrapper" program to drive my application. My application uses many data files every time it runs, so I have included these in the project/apps/application directory. They are downloaded correctly to the client, but when they are placed into the slot on the client, they are not copies of these files, but links. This is no good for my application, because it cannot resolve the filename to the actual file.

Is there some way that I can indicate that I need these files copied to the slot directory (something similar to the <copy_file/> tag for the input and output files)?

Thanks for any help!
ID: 27508 · Report as offensive
ryeterrell

Send message
Joined: 25 Aug 09
Posts: 23
United States
Message 27514 - Posted: 21 Sep 2009, 5:18:34 UTC - in response to Message 27508.  
Last modified: 21 Sep 2009, 5:24:03 UTC

One potential solution I have found is to prefix these data files with "$PROJECT_DIR" (http://boinc.berkeley.edu/trac/wiki/WrapperApp#Physicalfilemanagement). I'm now trying this. If I have a file named foo.bar, I rename it $PROJECT_DIRfoo.bar. Unfortunately, I am now getting "checksum or signature error"s when I try to download the workunit.

For the record, I use update_versions on the new app directory with these newly named files in it. It doesn't gripe about the other files in the application directory, only the prefixed ones.

Thanks for any help.
ID: 27514 · Report as offensive

Message boards : API : help with legacy application

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.