On Mon, Jan 25, 2016 at 4:59 PM, Peter Cock wrote:
> On Mon, Jan 25, 2016 at 4:44 PM, John Chilton wrote:
>> I think the problem is more that it is configured globally and not
>> per-destination. The real user stuff should all be per-destination and
>> not globally configured - since it should be
On Mon, Jan 25, 2016 at 4:44 PM, John Chilton wrote:
> I think the problem is more that it is configured globally and not
> per-destination. The real user stuff should all be per-destination and
> not globally configured - since it should be possible to have like a
> dedicated cluster for Galaxy j
I think the problem is more that it is configured globally and not
per-destination. The real user stuff should all be per-destination and
not globally configured - since it should be possible to have like a
dedicated cluster for Galaxy jobs that just run jobs normally and a
general purpose cluster
On Mon, Jan 25, 2016 at 3:33 PM, John Chilton wrote:
> On Mon, Jan 25, 2016 at 3:26 PM, Peter Cock wrote:
>> On Mon, Jan 25, 2016 at 11:33 AM, Peter Cock
>> wrote:
>>> Hello all,
>>>
>>> We're currently looking at changing our Galaxy setup to link user accounts
>>> with Linux user accounts for
On Mon, Jan 25, 2016 at 3:26 PM, Peter Cock wrote:
> On Mon, Jan 25, 2016 at 11:33 AM, Peter Cock
> wrote:
>> Hello all,
>>
>> We're currently looking at changing our Galaxy setup to link user accounts
>> with Linux user accounts for better cluster integration (running jobs as the
>> actual user
