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 <andy.ri...@hpe.com> wrote: >> 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 >> <jessica.nettelb...@gmail.com> 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 slurm folks also confirmed this is in fact how it works. >> What prompted me to ask the question was when you want to scrap the >> data and push it somewhere else you can't tell what zone the data is >> in. when you pull in a date from a slurm command into say perl, there >> is no way to immediately tell what zone the date is in. of course you >> can certainly query the system to see what the user has set. but to >> me this is a little muddy. >> >> i'd prefer the dates either come out in UTC or have a timezone >> appended to the output, though i suspect that's easier said then >> done... >> > > -- > Andy Riebs > andy.ri...@hpe.com > Hewlett-Packard Enterprise > High Performance Computing Software Engineering > +1 404 648 9024 > My opinions are not necessarily those of HPE > May the source be with you! > >
