I've asked this here before, but I'm hoping that there have been some
changes or updates and I missed the email:
What's the state of the art in terms of configuring permissions on
BLAST target files (specifically the MBF files) so that multiple
users can run searches against targets in a shared directory, make
use of cached index and sequence files, and not encounter the dreaded:
Error opening /common/data/nt.mbf
open: Permission denied
Fatal Error:
From perusing the list archives I see the following options:
------------------------------------------------------------------------
--------
* Make a custom BLAST target directory for every user (not enough
disk space, doesn't scale)
* Hack MPIBlast code to change the file permissions on the MBF files
(seems reasonable, but there must be some reason why it's not already
done. Probably concerns about users stepping on each other's jobs).
* Install pre and post scripts in my DRM to erase cached files after
each job is done (why have a cache at all?)
Is there another option that I'm missing here? How do folks handle
this at large-ish installations with multiple users who each may run
mpiblast jobs against shared targets?
-Chris Dwan
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Mpiblast-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mpiblast-users
