Thanks for explaining alnc.Good job.
www.coderewind.com
Best Place to hunt for Code
This message posted from opensolaris.org
___
perf-discuss mailing list
perf-discuss@opensolaris.org
Timothy Butler wrote:
>> - since noone at Sun cares about fixing dtksh I am
>> going to file a RFE
>> to get it removed.
>
> Isn't it required as part of CDE for Unix certification?
We're removing CDE from future versions of Solaris already.
dtksh though is planned to stay as part of that work si
> - since noone at Sun cares about fixing dtksh I am
> going to file a RFE
> to get it removed.
Isn't it required as part of CDE for Unix certification?
tim
This message posted from opensolaris.org
___
perf-discuss mailing list
perf-discuss@opensol
Stefan Parvu wrote:
> > Wow, I thought you were about to encourage something like:
> > - use of the SE Toolkit
> > - making libproc a stable interface
> > - adding a Sun::Solaris::Proc to Perl
>
> +1
> Sun::Solaris::Proc might be a nice thing to have in Perl.
I agree... but I ho
Brendan Gregg - Sun Microsystems wrote:
> On Fri, Jul 20, 2007 at 11:49:07PM +0200, Roland Mainz wrote:
[snip]
> > Now I am wondering whether it may be usefull to put all the tools in
> > /usr/proc/bin/ and /usr/bin/ps in a seperate "procsh" (= "process shell"
> > (more or less an add-on on top of
Hey,
> Wow, I thought you were about to encourage something like:
> - use of the SE Toolkit
> - making libproc a stable interface
> - adding a Sun::Solaris::Proc to Perl
+1
Sun::Solaris::Proc might be a nice thing to have in Perl.
> A decision you may have already made, would b
G'Day Roland,
On Fri, Jul 20, 2007 at 11:49:07PM +0200, Roland Mainz wrote:
>
> Hi!
>
>
>
> This is an old idea based on the observation that many process
> monitoring tools or scripts are more or less |fork()|-bombs, for example
> sdtprocess calls /usr/bin/ps for each cycle and other tool
