On 12/14/21 11:29 AM, Andreas Dilger via lustre-discuss wrote:
> The JobID is provided by the clients, the servers don't really care how
> it was generated.
It just has to be <= 32 chars (or is that < 32)
--
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet:
Cc: lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] Jobstats Support with Singularity Container
Hi Andreas,
we are currently running Lustre 2.12.5.
So we could use the introduced feature of the complex JobID.
As I understand the manual,
11:14
To: Andreas Dilger
Cc: lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] Jobstats Support with Singularity Container
Hi Andreas,
we are currently running Lustre 2.12.5.
So we could use the introduced feature of the complex JobID.
As I understand the manual, we could generate
ubject: Re: [lustre-discuss] Jobstats Support with Singularity Container
See the Lustre Operations Manual for options setting the JobID. You can set it
using fields like "%u" for UID, or you can set it per process group, or for the
whole node. For containers, you could set it for the pr
See the Lustre Operations Manual for options setting the JobID. You can set it
using fields like "%u" for UID, or you can set it per process group, or for the
whole node. For containers, you could set it for the process group when it
starts and it should be inherited by all processes in the
