Hi, Now to know all DTrace runtime option or D compiler option, the only way is from that user guide. Is it possible to just *list* all options in dtrace command line? Either like "cc" or like "zfs set all": # cc -x cc: Warning: illegal option -x usage: cc [ options] files. Use ''cc -flags'' for details # cc -flags -# Verbose mode -### Show compiler commands built by driver, no compilation -A<name[(tokens)]> Preprocessor predicate assertion -B<[static|dynamic]> Specify dynamic or static binding ..... [output is snipped] # zfs set all missing dataset name usage: set <property=value> <filesystem|volume|snapshot> ... The following properties are supported: PROPERTY EDIT INHERIT VALUES available NO NO <size> compressratio NO NO <1.00x or higher if compressed> creation NO NO <date> mounted NO NO yes | no origin NO NO <snapshot> ...... [output is snipped] Thanks, -Alex -- This message posted from opensolaris.org
Alex Peng <alex.peng at sun.com> writes:> Hi, > > Now to know all DTrace runtime option or D compiler option, the only way is from that user guide. Is it possible to just *list* all options in dtrace command line? Either like "cc" or like "zfs set all": > > # cc -x > cc: Warning: illegal option -x > usage: cc [ options] files. Use ''cc -flags'' for details > # cc -flags > -# Verbose mode > -### Show compiler commands built by driver, no compilation > -A<name[(tokens)]> Preprocessor predicate assertion > -B<[static|dynamic]> Specify dynamic or static binding > ..... [output is snipped] > > # zfs set all > missing dataset name > usage: > set <property=value> <filesystem|volume|snapshot> ... > > The following properties are supported: > > PROPERTY EDIT INHERIT VALUES > > available NO NO <size> > compressratio NO NO <1.00x or higher if compressed> > creation NO NO <date> > mounted NO NO yes | no > origin NO NO <snapshot> > ...... [output is snipped]Did you try just "dtrace" ? Boyd
Here is my "dtrace" only output, it is [-x opt[=val]], but what I
really want is:
- which options are there?
- for each option, which value is valid?
I do prefer following the "zfs set all" way, just list option and its
possible value.
-Alex
# dtrace
Usage: dtrace [-32|-64] [-aACeFGhHlqSvVwZ] [-b bufsz] [-c cmd] [-D name[=def]]
[-I path] [-L path] [-o output] [-p pid] [-s script] [-U name]
[-x opt[=val]] [-X a|c|s|t]
[-P provider [[ predicate ] action ]]
[-m [ provider: ] module [[ predicate ] action ]]
[-f [[ provider: ] module: ] func [[ predicate ] action ]]
[-n [[[ provider: ] module: ] func: ] name [[ predicate ] action ]]
[-i probe-id [[ predicate ] action ]] [ args ... ]
predicate -> ''/'' D-expression ''/''
action -> ''{'' D-statements ''}''
-32 generate 32-bit D programs and ELF files
-64 generate 64-bit D programs and ELF files
-a claim anonymous tracing state
-A generate driver.conf(4) directives for anonymous tracing
-b set trace buffer size
-c run specified command and exit upon its completion
-C run cpp(1) preprocessor on script files
-D define symbol when invoking preprocessor
-e exit after compiling request but prior to enabling probes
-f enable or list probes matching the specified function name
-F coalesce trace output by function
-G generate an ELF file containing embedded dtrace program
-h generate a header file with definitions for static probes
-H print included files when invoking preprocessor
-i enable or list probes matching the specified probe id
-I add include directory to preprocessor search path
-l list probes matching specified criteria
-L add library directory to library search path
-m enable or list probes matching the specified module name
-n enable or list probes matching the specified probe name
-o set output file
-p grab specified process-ID and cache its symbol tables
-P enable or list probes matching the specified provider name
-q set quiet mode (only output explicitly traced data)
-s enable or list probes according to the specified D script
-S print D compiler intermediate code
-U undefine symbol when invoking preprocessor
-v set verbose mode (report stability attributes, arguments)
-V report DTrace API version
-w permit destructive actions
-x enable or modify compiler and tracing options
-X specify ISO C conformance settings for preprocessor
-Z permit probe descriptions that match zero probes
--
This message posted from opensolaris.org
On Nov 30, 2008, at 9:40 PM, Alex Peng wrote:> Here is my "dtrace" only output, it is [-x opt[=val]], but what I > really want is: > > - which options are there? > - for each option, which value is valid?Hey Alex, That would be a great RFE. Please file it if you haven''t already. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl
Just filed a bug, CR 6777997. In short, I prefer to have a "dtrace -xv" or "dtrace --options"(or dtrace --flags). BTW, I also want to have a "dtrace --actions" and "dtrace --aggregations", yes, again, a short manual. -Alex -- This message posted from opensolaris.org
Alex Peng writes:> Just filed a bug, CR 6777997. > > In short, I prefer to have a "dtrace -xv" or "dtrace --options"(or dtrace --flags). > > BTW, I also want to have a "dtrace --actions" and "dtrace --aggregations", yes, again, a short manual.Shouldn''t these things appear in the dtrace(1M) man page, and in a very friendly format? Why burden the command itself with carrying man page text? -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677