actually, according to the slurm folks, you can set SLURM_TIME_FORMAT
to whatever you want. so prefacing
SLURM_TIME_FORMAT=%s scontrol show job
outputs all the time fields in epoch time...
On Mon, Feb 26, 2018 at 8:35 AM, Andy Riebs wrote:
>> you can certainly query the system to see what th
you can certainly query the system to see what the user has set
Alternatively, you can set your preferred timezone with the TZ
environment variable when you issue your Slurm commands.
On 02/26/2018 08:31 AM, Michael Di Domenico wrote:
On Sat, Feb 24, 2018 at 7:20 AM, Jessica Nettelblad
wrot
On Sat, Feb 24, 2018 at 7:20 AM, Jessica Nettelblad
wrote:
> So it seems to me, unix time is used for dates, which is then converted with
> localtime for certain output to be readable for humans. Since Slurm is a C
> program run in a Unix environment, that is also what I would expect.
Thanks, the
Hi Michael,
I also got curious where the conversion is done, so I looked into the code.
Scontrol gets dates like submit time in unix time from slurmctld, then
converts it to local time on the machine where the command scontrol show
job is executed.
This is seen in the code. Slurmctld uses unix t
On 24/02/18 05:51, Michael Di Domenico wrote:
some of those variables are spit out as dates. since the dates do
not include a timezone field how should that date field be assumed
to work? from the value i conclude that it's my localtime, but is
the date being stored as UTC and converted using
when i run 'scontrol -o -d show job jobid=' i get a long list of variables
some of those variables are spit out as dates. since the dates do not
include a timezone field how should that date field be assumed to
work? from the value i conclude that it's my localtime, but is the
date being stored