> Am 10.03.2021 um 16:29 schrieb Brian Andrus :
>
> Marcus is right here. Filtering the input so you don't have GIGO is on the
> admin.
>
> There are too many different languages/characters to expect that to be
> handled by slurm and would make it bulkier for most users with no benefit.
Well
Marcus is right here. Filtering the input so you don't have GIGO is on
the admin.
There are too many different languages/characters to expect that to be
handled by slurm and would make it bulkier for most users with no benefit.
Wrapper scripts and job_submit.lua are definitely your friends.
Yeah, I wondered something like that too, as it makes some of my scripts
quite fragile. I just tried your name on a test system and now calling
squeue paints my cli yellow :D
You could write a job_submit plugin to catch 'malicious' input, but so
far no user ever did something like that on our
On 3/10/21 12:06 PM, Reuti wrote:
Am 09.03.2021 um 13:37 schrieb Marcus Boden :
Then I have good news for you! There is the --delimiter option:
https://slurm.schedmd.com/sacct.html#OPT_delimiter=
Aha, perfect – thx. Maybe it should be noted in the man page for the "-p"/"-P".
Good idea. I c
> Am 09.03.2021 um 13:37 schrieb Marcus Boden :
>
> Then I have good news for you! There is the --delimiter option:
> https://slurm.schedmd.com/sacct.html#OPT_delimiter=
Aha, perfect – thx. Maybe it should be noted in the man page for the "-p"/"-P".
But this leads to another question: there is
Then I have good news for you! There is the --delimiter option:
https://slurm.schedmd.com/sacct.html#OPT_delimiter=
Best,
Marcus
On 09.03.21 12:10, Reuti wrote:
Hi:
Am 09.03.2021 um 08:19 schrieb Bjørn-Helge Mevik :
"xiaojingh...@163.com" writes:
I am doing a parsing job on slurm fields.
Hi:
> Am 09.03.2021 um 08:19 schrieb Bjørn-Helge Mevik :
>
> "xiaojingh...@163.com" writes:
>
>> I am doing a parsing job on slurm fields. Sometimes when one field is
>> too long, slum will limit the length with a “+”.
>
> You don't say which slurm command you are trying to parse the output
>
Hello, Mevik,
I tried the -p option and it worked.
Thank you for your reply!
Regards,
Xiaojing
> On Mar 9, 2021, at 3:19 PM, Bjørn-Helge Mevik wrote:
>
> "xiaojingh...@163.com" writes:
>
>> I am doing a parsing job on slurm fields. Sometimes when one field is
>> too long, slum will limit the
"xiaojingh...@163.com" writes:
> I am doing a parsing job on slurm fields. Sometimes when one field is
> too long, slum will limit the length with a “+”.
You don't say which slurm command you are trying to parse the output
from, but if it is sacctmgr, it has an option --parsable2(*)
specifically
Hello, ole,
Thank you for your reply. I forgot the -p option. I really works. Problem
solved!
Regards,
Xiaojing
> On Mar 9, 2021, at 2:56 PM, Ole Holm Nielsen
> wrote:
>
> On 3/9/21 5:06 AM, xiaojingh...@163.com wrote:
>> Hi, guys
>> I am doing a parsing job on slurm fields. Sometimes when
On 3/9/21 5:06 AM, xiaojingh...@163.com wrote:
Hi, guys
I am doing a parsing job on slurm fields. Sometimes when one field is too long,
slum will limit the length with a “+”. But I prefer to get the complete value
of that field. Do you know how can I achieve that? I do not want to specify the
Hi, guys
I am doing a parsing job on slurm fields. Sometimes when one field is too long,
slum will limit the length with a “+”. But I prefer to get the complete value
of that field. Do you know how can I achieve that? I do not want to specify the
length either coz it still cannot guarantee that
12 matches
Mail list logo
