getrusage() "works" on all platforms, AFAIK, at least in the POSIX sense: the
fields are there, and they may or may not be filled in, but everything will
compile. This is why I wonder if specifying a what usage ought to be logged
(including nothing) wouldn't make sense. If you're on a platform
On Sat, Jan 07, 2012 at 02:50:40PM +0100, Jeroen van Meeuwen (Kolab Systems)
wrote:
> I guess what remains is to figure out what other (current?)
> platforms support, and if the code can be made so to be compatible
> across the board. I don't think we currently have a complete and
> exhaustive lis
On 2012-01-07 6:05, Wesley Craig wrote:
I don't see a good reason to include code that digs around in /proc
when getrusage() has the exact same data. I think adding, e.g., I/O
to the telemetry calls would be peachy, either as a runtime option or
if someone wants to exercise their autoconf-foo, a
I don't see a good reason to include code that digs around in /proc when
getrusage() has the exact same data. I think adding, e.g., I/O to the
telemetry calls would be peachy, either as a runtime option or if someone wants
to exercise their autoconf-foo, at build time as appropriate to the plat
2012/1/6 Jeroen van Meeuwen (Kolab Systems) :
> On 2012-01-06 18:17, Olivier ROLAND wrote:
>>>
>>> Jeroen van Meeuwen wrote:
2011/7/13 Wesley Craig :
>
> I'd think you'd want to add this to telemetry_rusage(). Seems like you
> can get this data from getrusage() since kernel 2
On 2012-01-06 18:17, Olivier ROLAND wrote:
Jeroen van Meeuwen wrote:
2011/7/13 Wesley Craig :
I'd think you'd want to add this to telemetry_rusage(). Seems
like you
can get this data from getrusage() since kernel 2.6.22?
I can, and would like to, push this out to the
git.cyrusimap.org/cyru
>>
>> 2011/7/13 Wesley Craig :
>>>
>>> I'd think you'd want to add this to telemetry_rusage(). Seems like you
>>> can get this data from getrusage() since kernel 2.6.22?
>>>
>
> Hi there,
>
> apologies for bumping the old topic, but in preparation for what I think I
> want to have included in 2.5
On 2012-01-06 17:47, Bron Gondwana wrote:
On Fri, Jan 06, 2012 at 05:15:48PM +0100, Jeroen van Meeuwen (Kolab
Systems) wrote:
I can, and would like to, push this out to the
git.cyrusimap.org/cyrus-imapd master branch for inclusion as is in
2.5, if there's no objections.
Sounds good.
Done.
On Fri, Jan 06, 2012 at 05:15:48PM +0100, Jeroen van Meeuwen (Kolab Systems)
wrote:
> On 2011-07-13 8:43, Olivier ROLAND wrote:
> >Thanks, you are perfectly right :-)
> >
> >2011/7/13 Wesley Craig :
> >>I'd think you'd want to add this to telemetry_rusage(). Seems
> >>like you can get this data f
On 2011-07-13 8:43, Olivier ROLAND wrote:
Thanks, you are perfectly right :-)
2011/7/13 Wesley Craig :
I'd think you'd want to add this to telemetry_rusage(). Seems like
you can get this data from getrusage() since kernel 2.6.22?
Hi there,
apologies for bumping the old topic, but in prepa
Thanks, you are perfectly right :-)
2011/7/13 Wesley Craig :
> I'd think you'd want to add this to telemetry_rusage(). Seems like you can
> get this data from getrusage() since kernel 2.6.22?
>
> :wes
>
> On 12 Jul 2011, at 12:14, Olivier ROLAND wrote:
>> Linux kernel 2.6.20 and later supports p
I'd think you'd want to add this to telemetry_rusage(). Seems like you can get
this data from getrusage() since kernel 2.6.22?
:wes
On 12 Jul 2011, at 12:14, Olivier ROLAND wrote:
> Linux kernel 2.6.20 and later supports per process I/O accounting.
> You can access every process/thread's I/O re
12 matches
Mail list logo