Re: [PATCH] Read THREAD_CPUTIME clock from other processes.

[Dario Faggioli]

On Thu, 2010-12-23 at 09:21 -0800, Randy Dunlap wrote: 
> On Thu, 23 Dec 2010 17:21:43 +0100 Dario Faggioli wrote:
> 
> > Trying to read CLOCK_THREAD_CPUTIME_ID of a thread from outside
> > the process that spawned it with this code:
> > 
> >         if (clock_getcpuclockid(tid, &clockid) != 0) {
> >                 perror("clock_getcpuclockid");
> >                 exit(EXIT_FAILURE);
> >         }
> > 
> > results in this:
> >   ### Testing tid 24207: CPU-time clock for PID 24207 is 1.132371729 seconds
> >   ### Testing tid 24209: clock_getcpuclockid: Success
> > 
> > OTH, if full-fledged processes are involved, the behaviour is this:
> >   ### Testing tid 24218: CPU-time clock for PID 24218 is 0.001059305 seconds
> >   ### Testing tid 24220: CPU-time clock for PID 24220 is 1.044057391 seconds
> > 
> > Test programs available here: http://gitorious.org/clockid.
> 
> 
> "DNS service for this domain has expired with DNS Made Easy"  :(
> 
Yep, I saw that... It seems gitorious is having some sort of big big
problem! :-O

I've to run now, so, here's a really quick-&-dirty tar of the repo...

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa  (Italy)

http://retis.sssup.it/people/faggioli -- dario.faggioli@xxxxxxxxxx

Attachment: clockid.tar.bz2
Description: application/bzip-compressed-tar

Attachment: signature.asc
Description: This is a digitally signed message part