Re: [galaxy-dev] cluster access

Dear list, I had some time to dig into this. Since this is a quite old thread here is a wrap up: The problem was that galaxy uses the USER part of the email address (USER@DOMAIN) to determine the system user to submit jobs to a drmaa cluster (I need to submit jobs as real user). In my

Re: [galaxy-dev] cluster access

That's interesting. I didn't set this up on our system, but if the LDAP can tell Galaxy the real username, maybe we can avoid having to setup usern...@example.org aliases and insisting our users do that for logging into Galaxy. Hopefully some other SGE users can comment on how they got the

Re: [galaxy-dev] cluster access

Hi, sorry, I forgot this central piece of information: We also use Univa Grid Engine. What would be easier adapting galaxy's mapping to users or setting up email aliases? I would need to ask our cluster admins if they could realize this. Best, Matthias On 10.04.2017 16:39, Peter Cock

Re: [galaxy-dev] cluster access

This may depend on the cluster setup, and how Galaxy accesses it. What are you using? We use SGE (actually Univa Grid Engine) via DRMAA, and had to setup usern...@example.org email aliases just for this. Peter On Mon, Apr 10, 2017 at 3:36 PM, Matthias Bernt wrote: > Dear list,

[galaxy-dev] cluster access

Dear list, I'm just starting to get jobs submitted to our cluster as real system user. I read in the documentation that the name of the system user is determined by "the Galaxy user's email address (with the @domain stripped off)". But this does not work on our system, rather the username