Dan Nelson wrote:
> I was wondering why you were having so much trouble finding what you were
> looking for, and then I realized I have a patch that I have never submitted
> a PR for: the addition of "systime" and "usertime" ps keywords :) It simply
> reads the rusage struct, and returns the same v
On Sun, Mar 08, 2009 at 08:33:27PM -0400, Jay Loden wrote:
> Oliver Fromme wrote:
> > ps(1) and top(1) both use ki_pctcpu, see the getpcpu()
> > function in src/bin/ps/print.c and format_next_process()
> > in src/usr.bin/top/machine.c
>
> Hi Oliver, thanks for the reply. I noticed the same after s
In the last episode (Mar 08), Jay Loden said:
> Oliver Fromme wrote:
> > ps(1) and top(1) both use ki_pctcpu, see the getpcpu() function in
> > src/bin/ps/print.c and format_next_process() in
> > src/usr.bin/top/machine.c
>
> Hi Oliver, thanks for the reply. I noticed the same after some digging
>
Oliver Fromme wrote:
> ps(1) and top(1) both use ki_pctcpu, see the getpcpu()
> function in src/bin/ps/print.c and format_next_process()
> in src/usr.bin/top/machine.c
Hi Oliver, thanks for the reply. I noticed the same after some digging through
the source code for ps and top. While CPU usage % i
Jay Loden wrote:
> I'm working on FreeBSD support for a Python library called psutil for reading
> process information in a cross-platform fashion. Each platform-specific
> module
> is written in C, so the majority of the FreeBSD code is a C interface to
> various
> process information. I'v
I'm working on FreeBSD support for a Python library called psutil for reading
process information in a cross-platform fashion. Each platform-specific module
is written in C, so the majority of the FreeBSD code is a C interface to various
process information. I've been having some trouble working ou
6 matches
Mail list logo
