I wonder if it would work to grab iscsitgtd from Nevada and run it in place of 
the one in Solaris 10.  Certainly too risky for a production environment, but 
if you're just playing around....

Chip

Sent from my Windows MobileĀ® phone.

-----Original Message-----
From: Peter Cudhea <[email protected]>
Sent: Thursday, February 12, 2009 5:41 PM
To: Dan Mick <[email protected]>
Cc: [email protected] <[email protected]>; C V 
<[email protected]>
Subject: Re: [dtrace-discuss] iscsi provider

The DTrace provider for iscsi has not been ported back to S10.  As far 
as I know there are no current plans to do so.

Peter

Dan Mick wrote:
> C V wrote:
>> According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider 
>> and http://wikis.sun.com/display/DTrace/iscsi+Provider there should 
>> be a dtrace provider for iscsi. However, on Solaris 10 10/08, there 
>> doesn't seem to be one. Should there be? If so, how do I get it enabled?
>>
>> [r...@sol10-1 /]# dtrace -ln 'iscsi*:::'
>>    ID   PROVIDER            MODULE                          FUNCTION 
>> NAME
>> dtrace: failed to match iscsi*:::: No probe matches description
>> [r...@sol10-1 /]# cat /etc/release                        Solaris 10 
>> 10/08 s10x_u6wos_07b X86
>>
>> Thanks
>> -- 
>> CV
>
> It's not clear to me it's in 10/08, but, on relatively-recent Nevada, 
> that dtrace command shows no output either.  I didn't think USDT 
> probes allowed wildcarding the PID.
>
> dtrace -ln "ksh*:::"
>    ID   PROVIDER            MODULE                          FUNCTION NAME
> dtrace: failed to match ksh*:::: No probe matches description
>
> I don't have an iscsitgtd process to try it with.
> _______________________________________________
> dtrace-discuss mailing list
> [email protected]
_______________________________________________
dtrace-discuss mailing list
[email protected]


_______________________________________________
dtrace-discuss mailing list
[email protected]

Reply via email to