From: Jan-Frode Myklebust <janfrode@parallab.no>
To: John Hesterberg <jh@sgi.com>
Cc: linux-kernel@vger.kernel.org, csa@oss.sgi.com, pagg@oss.sgi.com,
Robin Holt <holt@sgi.com>
Subject: Re: [PATCH] 2.5.44 CSA, Job, and PAGG
Date: Wed, 23 Oct 2002 23:20:37 +0200 [thread overview]
Message-ID: <20021023232037.A3752@ii.uib.no> (raw)
In-Reply-To: <20021023145342.A6595@sgi.com>; from jh@sgi.com on Wed, Oct 23, 2002 at 02:53:42PM -0500
I see the struct acctcsa has a ac_prid.. Are you planning on adding
project level accounting to linux, or is this just leftovers from
IRIX?
I'm not familiar with CSA, but have some experience with using the
IRIX system audit trail for accounting (satd). satd isn't handling the
accounting very well when we get hard hangs or power outages, and no
end-of-job record is written. Then we have no account for the cpu-usage
of the non-finished jobs at the time.
Does CSA handle this better, or is it still depending on jobs being
finished before writing any accounting records? (a way telling it to
log periodic intermidiate accounting records would be nice)
-jf
next prev parent reply other threads:[~2002-10-23 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:53 [PATCH] 2.5.44 CSA, Job, and PAGG John Hesterberg
2002-10-23 21:20 ` Jan-Frode Myklebust [this message]
2002-10-23 21:35 ` Robin Holt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021023232037.A3752@ii.uib.no \
--to=janfrode@parallab.no \
--cc=csa@oss.sgi.com \
--cc=holt@sgi.com \
--cc=jh@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pagg@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.