Re: Is describing sysctl variables useful?

2008-04-06 Thread Dag-Erling Smørgrav
David Wolfskill <[EMAIL PROTECTED]> writes: > To that end, I've cobbled up a Perl script that acts as a "wrapper" > around time(1) and uses that command to obtain the "rusage" (ref. > getrusage(2)) information about the command in question. http://search.cpan.org/~taffy/Unix-Getrusage-0.03/ DES -

Re: Is describing sysctl variables useful?

2008-04-06 Thread Sofian Brabez
On Fri, Apr 4, 2008 at 10:36 AM, Alexander Leidinger <[EMAIL PROTECTED]> wrote: > Unfortunately this is not suitable for the SoC. Google wants code > contributions, not pure documentation work. Maybe you can find something > else you would be willing to do during the SoC. In case you haven't send

Re: Is describing sysctl variables useful?

2008-04-04 Thread David Wolfskill
On Fri, Apr 04, 2008 at 07:32:46PM +1100, Peter Jeremy wrote: > ... > Whilst not addressing your issues with sysctl, have you considered > using process accounting (acct(5) and sa(8))? Yes, but I have the impression (of which I wouldn't mind being disabused) that that approach would perturb the sy

Re: Is describing sysctl variables useful?

2008-04-04 Thread Ivan Voras
Alexander Leidinger wrote: > Quoting Sofian Brabez <[EMAIL PROTECTED]> (from Fri, 4 Apr 2008 05:11:41 > +0200): > >> About syscl(3) OID description lack, i send my Google Summer Code >> application to complete it this summer ;). > > Unfortunately this is not suitable for the SoC. Google wants co

Re: Is describing sysctl variables useful?

2008-04-04 Thread Alexander Leidinger
Quoting Sofian Brabez <[EMAIL PROTECTED]> (from Fri, 4 Apr 2008 05:11:41 +0200): About syscl(3) OID description lack, i send my Google Summer Code application to complete it this summer ;). Unfortunately this is not suitable for the SoC. Google wants code contributions, not pure documenta

Re: Is describing sysctl variables useful?

2008-04-04 Thread Peter Jeremy
On Thu, Apr 03, 2008 at 01:26:20PM -0700, David Wolfskill wrote: >To that end, I've cobbled up a Perl script that acts as a "wrapper" >around time(1) and uses that command to obtain the "rusage" (ref. >getrusage(2)) information about the command in question. Whilst not addressing your issues with

Re: Is describing sysctl variables useful?

2008-04-03 Thread Sofian Brabez
About syscl(3) OID description lack, i send my Google Summer Code application to complete it this summer ;). I identify alls lacks in sysctl at http://6dev.net/~sbz/sysctl.txt and i want to correct them during Google Summer Code. My application was sent since 30 March 2008 via Google student Web

Re: Is describing sysctl variables useful?

2008-04-03 Thread Elijah Buck
The project that Niki is referring to is something I've begun working on as part of a independent project for school. Sysctl documentation strings are definitely wanted. Mat (@freeebsd) has a partially complete sysctl documentation branch in perforce (//depot/user/mat/src/sysctl_cleanup/). You migh

Re: Is describing sysctl variables useful?

2008-04-03 Thread Niki Denev
On Thu, Apr 3, 2008 at 11:26 PM, David Wolfskill <[EMAIL PROTECTED]> wrote: > At work, I'm trying to get some measurements for what is going on on > various systems, especially when developers are trying to use them. > (The goal is to improve the situation; measurement is a rather early > step in t

Is describing sysctl variables useful?

2008-04-03 Thread David Wolfskill
At work, I'm trying to get some measurements for what is going on on various systems, especially when developers are trying to use them. (The goal is to improve the situation; measurement is a rather early step in that process.) To that end, I've cobbled up a Perl script that acts as a "wrapper" a