Lines Matching refs:scripts

17 	scripts provided, but also due to the role it would play: few people
19 we would like a majority of Solaris users to write DTrace scripts,
22 a dozen scripts, man pages and a structure for documentation.
33 each, but I've found having them as seperate scripts makes them far
34 easier to find and use. The scripts and man page for each script do
38 Version 0.33 with 33 scripts. Maybe I should make the version number
49 Version 0.35 with 35 scripts. Also touched up procsystime and some
53 Added 7 more scripts.
56 Added heaps of new scripts. Now at 57 scripts.
63 variants of classic scripts while writing dexplorer, and have added
69 dropped tcpwbytes.d and tcpwlist. These are complex scripts, but they
71 complex scripts, I expect they will require maintainence for newer
75 Also added iotop, and updated a bunch of scripts. A lot of work went
77 (I'm still keeping the version number == to number of scripts).
81 Many new scripts added, many updates. This is a major release.
84 A few scripts have been updated so that they work better.
100 Many scripts were updated. Added the Apps category. I had planned
101 to add some key scripts, but they haven't made it out of testing yet.
108 Added a few scripts including rwbytype.d. Fixed several issues.
115 Internals, I've had numerous new ideas for DTrace scripts. Not only
117 tested, well considered DTrace scripts for inclusion in the toolkit.
120 Stefan Parvu sent me a bug for the tcp* scripts: on build 31+ they
123 same way). Ironically, when I first wrote the scripts I had hardcoded
132 the style that these scripts obey. It is quite strict, and sets
134 people to ever contribute scripts, which is fine. At some point
144 The toolkit now contains 104 scripts, however I'll keep the version
145 number < 1.00 until the dust has settled on these new scripts.
149 There is a new main directory, FS for file system related scripts.
150 There are some interesting scripts in there, from or based on
179 as it will indirectly help the tcp* scripts become more stable. Yes,
180 those scripts have broken a few more times during the last 18 months,
182 network providers. This is why I only ever wrote three tcp* scripts,
206 Many of the exciting new language provider scripts in this release
211 Good: many more scripts to cover the new DTrace language providers
212 that are available (the DTraceToolkit is now 227 scripts). Many
214 other than for scripts: Code - for simple programs to DTrace (and
223 JavaScript, Shell and Tcl. I've written about 15 scripts for each
225 The scripts are also similar from one language to another, having
226 devoleped a tried-and-tested group of scripts for analyzing real world
227 issues - it made sense to repeat these scripts for every language
237 this release while I focused on writing and testing the scripts.
242 The future: I still have many new scripts and some bug fixes in mind,