Re: getrusage vs /proc/pid/stat?

2001-06-19 Thread Dan Kegel
"J . A . Magallon" wrote: > I have just the same problem. getrusage() did not catch the CPU time for > children, even if the man page said that. Now I am using times(2), that > seems to work in Solaris, but gives nothing in Linux. > > I you look at time(1) manpage, it says time is implemented

Re: getrusage vs /proc/pid/stat?

2001-06-19 Thread Dan Kegel
J . A . Magallon wrote: I have just the same problem. getrusage() did not catch the CPU time for children, even if the man page said that. Now I am using times(2), that seems to work in Solaris, but gives nothing in Linux. I you look at time(1) manpage, it says time is implemented over the

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread J . A . Magallon
On 20010618 Dan Kegel wrote: >Pete Wyckoff wrote: >> >> [EMAIL PROTECTED] said: >> > I'd like to monitor CPU, memory, and I/O utilization in a >> > long-running multithreaded daemon under kernels 2.2, 2.4, >> > and possibly also Solaris (#ifdefs are ok). >> >> getrusage() isn't really the

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread Dan Kegel
Pete Wyckoff wrote: > > [EMAIL PROTECTED] said: > > I'd like to monitor CPU, memory, and I/O utilization in a > > long-running multithreaded daemon under kernels 2.2, 2.4, > > and possibly also Solaris (#ifdefs are ok). > > getrusage() isn't really the system call you want for this. I'll buy

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread Pete Wyckoff
[EMAIL PROTECTED] said: > I'd like to monitor CPU, memory, and I/O utilization in a > long-running multithreaded daemon under kernels 2.2, 2.4, > and possibly also Solaris (#ifdefs are ok). > > getrusage() looked promising, and might even work for CPU utilization. > Dunno if it returns info for

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread Pete Wyckoff
[EMAIL PROTECTED] said: I'd like to monitor CPU, memory, and I/O utilization in a long-running multithreaded daemon under kernels 2.2, 2.4, and possibly also Solaris (#ifdefs are ok). getrusage() looked promising, and might even work for CPU utilization. Dunno if it returns info for all

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread Dan Kegel
Pete Wyckoff wrote: [EMAIL PROTECTED] said: I'd like to monitor CPU, memory, and I/O utilization in a long-running multithreaded daemon under kernels 2.2, 2.4, and possibly also Solaris (#ifdefs are ok). getrusage() isn't really the system call you want for this. I'll buy that.

Re: getrusage vs /proc/pid/stat?

2001-06-18 Thread J . A . Magallon
On 20010618 Dan Kegel wrote: Pete Wyckoff wrote: [EMAIL PROTECTED] said: I'd like to monitor CPU, memory, and I/O utilization in a long-running multithreaded daemon under kernels 2.2, 2.4, and possibly also Solaris (#ifdefs are ok). getrusage() isn't really the system call you want

getrusage vs /proc/pid/stat?

2001-06-17 Thread Dan Kegel
I'd like to monitor CPU, memory, and I/O utilization in a long-running multithreaded daemon under kernels 2.2, 2.4, and possibly also Solaris (#ifdefs are ok). getrusage() looked promising, and might even work for CPU utilization. Dunno if it returns info for all child threads yet, haven't

getrusage vs /proc/pid/stat?

2001-06-17 Thread Dan Kegel
I'd like to monitor CPU, memory, and I/O utilization in a long-running multithreaded daemon under kernels 2.2, 2.4, and possibly also Solaris (#ifdefs are ok). getrusage() looked promising, and might even work for CPU utilization. Dunno if it returns info for all child threads yet, haven't