most users with no benefit.
Well, yes. I can see the point. The longterm solution might be to exclude
characters 0x00–0x1F and/or allow only printable UTF-8 characters with proper
spacing in `squeue` and alike, as some characters take 2 or more bytes. for
their representation.
-- Reuti
> Wrapp
leads to another question: there is no well defined character set for
allowed job names, and I can have a job:
$ sbatch --job-name="fu"$'\007'$'\033[32m'"bar" slurm-job.sh
which might make some noise when using `squeue` and messes up the output?
-- Reu
> the line, so I prefer --parsable2.
It would even be better to have the option to use an argument for these two
options or even --parsable='`\000' like in `tr`. For now users can use "|" in
jobname, account or comment which might break any parsing.
-- Reuti
> --
> Cheers,
> Bjørn-Helge Mevik, dr. scient,
> Department for Research Computing, University of Oslo
>
ht also get reset, if it's not working
after an `rpm -U ssh`, check this flag.
-- Reuti
use ~${SLURM_JOB_USER} to access their semaphore file.
To use ~${SLURM_JOB_USER} it should be necessary to use `eval`, as it needs to
be evaluated twice. More promising might be:
$ getent passwd ${SLURM_JOB_USER} | cut -d: -f6
-- Reuti
> Potentially problematic for any sites with hom
nse by another instance of this application,
being it the same or another machine. Often the state of the license daemon can
be checked and the stopped application should allow the counter of the
available licenses to increment again in the license daemon's state output.
-- Reuti
> A
t;after:runB-step1" …
Some workflow using these dependencies could be set up without knowing any
beforehand then.
-- Reuti
> Am 22.10.2019 um 11:55 schrieb Florian Lohoff :
>
> On Tue, Oct 22, 2019 at 12:06:57PM +0300, mercan wrote:
>> Hi;
>>
>> You can use
sure that there is no access to /home slowing down the
cluster and interactive work on the login node.
-- Reuti
ehow like
Condor does it IIRC.
-- Reuti
d by any of the processes will be
returned to the job script and no application error is raised. Hence one can
act on this return code in a proper way in the job script.
-- Reuti
> to fix in my queue, that's where we left it.
Thanks for the info. Good to know to try this in case a problem arises.
Surprisingly enough this was one feature I liked in SGE and always recommend
not to use -V there, as the acutal environment might corrupt the job script.
-- Reuti
Hi,
> Am 22.03.2019 um 16:20 schrieb Prentice Bisbal :
>
> On 3/21/19 6:56 PM, Reuti wrote:
>> Am 21.03.2019 um 23:43 schrieb Prentice Bisbal:
>>
>>> Slurm-users,
>>>
>>> My users here have developed a GUI application which serves as a GUI
>&
> Am 22.03.2019 um 16:20 schrieb Prentice Bisbal :
>
> On 3/21/19 6:56 PM, Reuti wrote:
>> Am 21.03.2019 um 23:43 schrieb Prentice Bisbal:
>>
>>> Slurm-users,
>>>
>>> My users here have developed a GUI application which serves as a GUI
>&
can take to get more debug information?
Was an alias to `mpirun` introduced? It may cover the real application and even
the `which mpirun` will return the correct value, but never be executed.
$ type mpirun
$ alias mpirun
may tell in the jobscript.
-- Reuti
t; issues, and have a plan to revert to an earlier version if issues are
> discovered. This is work, but it's really not all that much work, and this is
> exactly the work we are being paid to do as cluster admins.
Besides the work on the side of the admins, also the users are involved:
15 matches
Mail list logo
