I knew we weren’t alone! Thanks, Juergen!
If the scheduling engine was slightly better for reservations (eg. “Third
Tuesday” type stuff), it would probably happen a little less often. I know it’s
sort of getting there.
--
#BlackLivesMatter
____
|| \\UTGERS, |---------------------------*O*---------------------------
||_// the State | Ryan Novosielski - novos...@rutgers.edu
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
|| \\ of NJ | Office of Advanced Research Computing - MSB C630, Newark
`'
> On Apr 16, 2021, at 6:21 PM, Juergen Salk <juergen.s...@uni-ulm.de> wrote:
>
> * Ryan Novosielski <novos...@rutgers.edu> [210416 21:33]:
>
>> Does anyone have a particularly clever way, either built-in or
>> scripted, to find out which jobs will still be running at
>> such-and-such time?
>
> Hi Ryan,
>
> coincidentally, I just did this today. For exactly the same reason.
> squeue does have a "%L" format option which will print out the time
> left for the jobs in days-hours:minutes:seconds.
>
> For example: squeue -t r -o "%u %i %L"
>
> This may help to identify jobs that already started and may
> eventually run into a maintenance reservation.
>
>> I bet anyone who’s made the mistake of not
>> entering a maintenance reservation soon enough knows the feeling.
>
> Yes. ;-)
>
> Best regards
> Jürgen
>
>
