Hi, I remember this question occuring before, but the answer usually was not straightforward. Example:
https://groups.google.com/forum/?_escaped_fragment_=topic/slurm-devel/G8iTMHMTXMU#!topic/slurm-devel/G8iTMHMTXMU
The (for a Torque/Maui user) simple idea of appending to the user's job
log file(s) from prologue/epilogue scripts seems not to be part of
Slurm's mindset. I consider it only natural that printouts to stdout
and stderr from the prologue/epilogue scripts end up somehow in the job
log files.
What is the current way, the best practice, to add something to the job
output? Is a SPANK plugin, picking a callback and there producing the
desired output, the only proper thing to do?
My motivation is to push information about used resources, gathered by
our scripts also with stuff Slurm does not care about, to the user
(best in log file and also in the mail sent after completion) instead
of having the user actively asking for it. Because they don't ask for
it if they don't think that they are doing something wrong …
The simplest kind of message to bring across would be
Note: Your total CPU usage is rather low. This might be due to I/O
delays or sub-optimal parallelization. Please consider optimizing
this type of job.
This used to be easy with Torque … just echo >&2 in the epilogue script
… is it still a challenge with Slurm?
Alrighty then,
Thomas
--
Dr. Thomas Orgis
Universität Hamburg
RRZ / Zentrale Dienste / HPC
Schlüterstr. 70
20146 Hamburg
Tel.: 040/42838 8826
Fax: 040/428 38 6270
smime.p7s
Description: S/MIME cryptographic signature
