Thanks indeed for the ~/.slurm_drmaa.conf hint Mariusz, very useful ! I wonder how this approach will work out when one runs galaxy as advised in a production setting: http://usegalaxy.org/production Together with the gordon patch to run drmaa as different users: http://wiki.g2.bx.psu.edu/Events/GCC2011?action=AttachFile&do=get&target=RunningGalaxyDRMAAJobsAsDifferentUsers.pdf My concern is that probably the SUID code will end up clearing up all the environment variables and/or ignoring the user's ~/.slurm_drmaa.conf as happened to me before with "screen": http://superuser.com/questions/235760/ld-library-path-unset-by-screen I'll jump in that Gordon patch/code eventually, but for now your insight/fixes have been very helpful from a galaxy developer instance perspective, thanks much again ! /Roman On 2011-07-19 19:53, Mariusz MamoĊski wrote:
The general config file allows us to set a fixed project:
default_cluster_job_runner = drmaa://-A a2010002 -p core
And even set per-tool job settings. But we would like each user to have the ability to change those settings.
What is the least intrusive way to set per-user native (site-specific) job manager settings ?
you may try to use an user's local DRMAA configuration file:
~/.slurm_drmaa.conf
". If multiple configuration sources are present then all configurations are merged with values from user-defined files taking precedence (in following order: $SLURM_DRMAA_CONF, ~/.slurm_drmaa.conf, /etc/slurm_drmaa.conf)"
there you can put any user's specific settings, e.g.:
job_categories: { default: "-A a2010002 -p core", }
Cheers,