To All (This is mainly for the Mac DTrace 3, Adam Leventhal, Bryan
Cantrill, Mike Shapiro),
My name is Blake Sawyer and I am currently doing some research at
Virginia Tech. One of the goals of this project is to track
meaningful user interactions such as viewing any file, webpage, or
On 09/02/08 08:07, Blake Sawyer wrote:
To All (This is mainly for the Mac DTrace 3, Adam Leventhal, Bryan
Cantrill, Mike Shapiro),
My name is Blake Sawyer and I am currently doing some research at
Virginia Tech. One of the goals of this project is to track
meaningful user
To All (This is mainly for the Mac DTrace 3, Adam Leventhal, Bryan
Cantrill, Mike Shapiro)..
We appreciate your desire to go to the source. It's a lot like posting a
question on
relativity, and indicating you'd really like an answer from Einstein :^)
That said, there's great news -
and there are many, many DTrace experts that can help. So Brian, Mike and
Sorry; s/Brian/Bryan
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Jim,
Thanks so much for your help. Also thanks for understanding my
terminology mistakes, I am new to a lot of this. Let me clear some of
these things up by explaining the idea of my project.
I want to create an indexing application that will work with a
location/context aware system.
| I want to create an indexing application that will work with a
| location/context aware system. This application will automatically
| index media files(documents, video, audio, webpages, mail, etc.)
| socially and episodically. For example, in a meeting scenario, the
| system will
Brian Utterback writes:
So, two comments:
1. This is a case where a more general error message would probably
have been more helpful than the more specific ones.
True.
2. Why can't they be combined? If the data recording actions are not
after a speculate, I don't even see how they are
I'm not sure I can add anything beyond Bryan's response.
I'm not an expert in WEB servers or the multimedia server stack
(other software components that get integrated for building these
cool sites), but I would first look at add-ons, compiler flags, options,
etc, for the actual software
Hello dtrace gurus,
Is it possible to put DTRACE_PROBEs in a driver attach routine, and
expect to see them show up when running a dtrace script to trigger them
(which incidentally causes the driver to be modload-ed)?
I'm trying to change all of the funky con_log() calls in the mega_sas
driver
On Tue, Sep 02, 2008 at 03:47:25PM -0700, Susan Scheufele wrote:
Hello dtrace gurus,
Is it possible to put DTRACE_PROBEs in a driver attach routine, and
expect to see them show up when running a dtrace script to trigger them
(which incidentally causes the driver to be modload-ed)?
I'm
Hi Jonathan,
I am running snapshot 96. The boot drive is using the mpt driver.
And the same thing happens -- no output, although the driver has been
modloaded via running the dtrace command (and I did wait a bit before
typing ctrlc).
dell690pr# modinfo | grep mpt
46 f7883000 3c768
Dtrace does not like your suggestion:
dell690pr# dtrace -Fn '\
fbt:mega_sas::entry{}\
fbt:mega_sas::entry/count++ = 60/{exit(0);}\
'
dtrace: invalid probe specifier
fbt:mega_sas::entry{}
fbt:mega_sas::entry/count++ = 60/{exit(0);}
: in predicate: aggregating function 'count' may not be referenced
12 matches
Mail list logo