Hi Janne,
On Thu, Apr 13, 2017 at 1:32 AM, Janne Blomqvist
wrote:
> Should work as of 16.05 unless you have some very peculiar setup. IIRC I
> submitted some patch to get rid of the enumeration entirely, but
> apparently SchedMD has customers who have multiple groups
Hi Wensheng,
On Thu, Apr 13, 2017 at 6:23 AM, Wensheng Deng wrote:
> Hi, several months ago when I started learning Slurm and reading through the
> web pages, I made this picture to help myself understanding the *prolog and
> *epilog interactions with job steps. Please see the
A recent post on Slurm training prompted me to mention that I created for our
users the following guides to using Slurm:
https://hpc.llnl.gov/banks-jobs/running-jobs
The Batch System Primer introduces new users to HPC batch scheduling concepts.
The Slurm User Manual and Quick Start Guide
Thank you!
Doug
From: Merlin Hartley [mailto:merlin-sl...@mrc-mbu.cam.ac.uk]
Sent: Thursday, April 13, 2017 7:00 AM
To: slurm-dev
Subject: [slurm-dev] Re: Slurm Light?
You can just disable accounting altogether by commenting these lines:
You can just disable accounting altogether by commenting these lines:
#JobAcctGatherType=jobacct_gather/linux
#JobAcctGatherFrequency=30
#AccountingStorageType=accounting_storage/slurmdbd
#AccountingStorageHost=
#AccountingStorageLoc=
Hello everyone,
I'm looking for a way to properly catch an incoming srun/salloc/etc.
command, check which node its supposed to run on, and possibly redirect
it to some other node of my choosing.
All of this from within the code.
My current point of invasion is within the scheduler plugin.
We would like to use slurm in its most stripped down form for very small
environments. I can see the options in the slurm.conf to use text files vice a
database for accounting and logs. Is there a mechanism obviating the need for
accounts and user definition thus allowing us to skip
Hi, several months ago when I started learning Slurm and reading through
the web pages, I made this picture to help myself understanding the *prolog
and *epilog interactions with job steps. Please see the attachment. If you
see any corrections necessary, please inform. Thank you!
Best Regards.
Il 13/04/2017 14:26, Janne Blomqvist ha scritto:
> We use adcli (there's an rpm package called adcli in EL7, FWIW; upstream
> seems to be http://cgit.freedesktop.org/realmd/adcli ).
Uhm... I didn't know it. BTW I use Debian for the servers.
> Not sure how any of this would work with colliding
On 2017-04-13 15:09, Diego Zuccato wrote:
>
> Il 12/04/2017 08:52, Janne Blomqvist ha scritto:
>
>> BTW, do you have some kind of trust relationship between your FreeIPA
>> domain and the AD domain, or how do you do it? I did play around with
>> using FreeIPA for our cluster as well and somehow
Il 12/04/2017 08:52, Janne Blomqvist ha scritto:
> BTW, do you have some kind of trust relationship between your FreeIPA
> domain and the AD domain, or how do you do it? I did play around with
> using FreeIPA for our cluster as well and somehow synchronizing it with
> the university AD domain,
On 2017-04-13 02:30, Christopher Samuel wrote:
>
> On 13/04/17 01:47, Jeff White wrote:
>
>> +1 for Active Directory bashing.
>
> I wasn't intending to "bash" AD here, just that the AD that we were
> trying to use (and I suspect that Lachlan might me talking to) has tens
> of thousands of
Hi Roger,
instead of canceling the job normally, the user could use "scancel --signal=
" in order to send a specific signal to his jobscript or application.
His application/jobscript now should be able to handle that signal and after
performing the cleanup tasks it can terminate its self
13 matches
Mail list logo