<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>All the aggregate historic data should be accessible via sacct. 
      sstat is for live jobs but sacct is for completed jobs.</p>
    <p>-Paul Edmon-<br>
    </p>
    <div class="moz-cite-prefix">On 10/30/2019 2:13 PM, Jacob Chappell
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CA+8pZc_ECiQmOU6gkiCrSwnb2iDqD2mMPwGxM06d+xddXf24EA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>Is there a simple way to store sstat information
          permanently on job completion? We already have job accounting
          on, but the information collected from cgroups doesn't seem to
          be stored once a job finishes (sstat -j $JOB_ID on a dead job
          returns an error).</div>
        <div><br>
        </div>
        <div>Thanks,<br>
        </div>
        <div>
          <div>
            <div dir="ltr" class="gmail_signature"
              data-smartmail="gmail_signature">
              <div dir="ltr">
                <div>
                  <div dir="ltr">
                    <div>
                      <div dir="ltr">
                        <div>
                          <div dir="ltr">
                            <div>
                              <div dir="ltr"><span
                                  style="font-family:arial,helvetica,sans-serif"><span
                                    style="color:rgb(7,55,99)"><font
                                      size="2">____</font></span></span><span
                                  style="color:rgb(7,55,99)"><font
                                    size="2"><span
                                      style="font-family:arial,helvetica,sans-serif"><span><span
style="font-family:arial,helvetica,sans-serif">_____</span></span></span><span
style="font-family:arial,helvetica,sans-serif"><span><span
                                          style="font-family:arial,helvetica,sans-serif"><span><span
style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span><span
style="font-family:arial,helvetica,sans-serif"><span><span
                                          style="font-family:arial,helvetica,sans-serif"><span><span
style="font-family:arial,helvetica,sans-serif"><span><span
                                                  style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span></span></span><span
style="font-family:arial,helvetica,sans-serif"><span><span
                                          style="font-family:arial,helvetica,sans-serif"><span><span
style="font-family:arial,helvetica,sans-serif"><span><span
                                                  style="font-family:arial,helvetica,sans-serif"><span><span
style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span></span>_____</span></span>______<br>
                                      <b>Jacob D. Chappell, CSM</b><br>
                                      <b>Research Computing Associate</b><br>
                                      Research Computing | Research
                                      Computing Infrastructure<br>
                                      Information Technology Services |
                                      University of Kentucky<br>
                                      <a
                                        href="mailto:jacob.chappell@uky.edu"
                                        target="_blank"
                                        moz-do-not-send="true">jacob.chappell@uky.edu</a><br>
                                    </span></font></span></div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>