Sponsored Content
Operating Systems Solaris Setting up a Solaris training Post 302249659 by pupp on Tuesday 21st of October 2008 07:13:03 PM
Old 10-21-2008
i think dtrace is going beyond what they may need to know. advanced debugging should not be a field engineer's task.

dtrace alone could be a week long class.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX/solaris training

I am new to UNIX and somewhat familiar with Solaris. Can you suggest any good (simple English) books that can help me with understanding and learning UNIX? (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

2. UNIX for Dummies Questions & Answers

Solaris for a training: PC vs Sparc

I need a computer to try Solaris. I'm learning with UNIX Academy training DVDs and after spending much time with Linux I want to try and learn on Solaris. I'll have to buy a computer for my training anyway. I found on ebay plenty of inexpensive Sun boxes. Would it be beneficial for learning to have... (26 Replies)
Discussion started by: newlinuxuser1
26 Replies

3. Solaris

Setting IP on Solaris 10 help

Hi all, So, I need to change the IP/netmask on 2 sun v240's running solaris 10. I seem to have done it correctly on one, it's holding the ip after a init 6 reboot. The other does not want to keep ip using same commands. I'm guessing I have to change some files I haven't yet, but have no... (7 Replies)
Discussion started by: kuriosity_prime
7 Replies

4. UNIX for Beginners Questions & Answers

Any Solaris training?

Good Afternoon, Does anyone know of any free or cheap SkillSoft type Solaris training, with an exam? (0 Replies)
Discussion started by: Stellaman1977
0 Replies
DTRACE(1)						      General Commands Manual							 DTRACE(1)

NAME
dtrace - Dtrace compatibile user application static probe generation tool. SYNOPSIS
dtrace -s file [OPTIONS] DESCRIPTION
The dtrace command converts probe descriptions defined in file.d into a probe header file via the -h option or a probe description file via the -G option. OPTIONS
-h generate a systemtap header file. -G generate a systemtap probe definition object file. -o file is the name of the output file. If the -G option is given then the output file will be called file.o; if the -h option is given then the output file will be called file.h. -C run the cpp preprocessor on the input file when the -h option is given. -I file give this include path to cpp when the -C option is given. -k keep temporary files, for example the C language source for the -G option. --types generate probe argument typedef information when the -h option is given. EXAMPLES
Systemtap is source compatible with dtrace user application static probe support. Given a file test.d containing: provider sdt_probes { probe test_0 (int type); probe test_1 (struct astruct node); }; struct astruct {int a; int b;}; Then the command "dtrace -s test.d -G" will create the probe definition file test.o and the command "dtrace -s test.d -h" will create the probe header file test.h Subsequently the application can define probes using #include "test.h" ... struct astruct s; ... SDT_PROBES_TEST_0(value); ... SDT_PROBES_TEST_1(s); The application is linked with "test.o" when it is built. SEE ALSO
stap(1) stappaths(7) DTRACE(1)
All times are GMT -4. The time now is 09:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy