Daniel,
You are running a very old Solaris 10 update, and a very old kernel
patch! Based on that, I think it's quite possible that your other
patches are "sub-optimal". Seriously dude, you should make patching and
upgrading a priority. I have a hunch that once you're running something
sensible your DTrace problem will just go away (and your whole life will
probably improve too). My recommendation would be to take a full backup,
and then go straight for an upgrade install of the latest Solaris 10
update (i.e. don't patch).
Phil
Qihua Wu wrote:
The dtrace script supposed to print out every 1 second, but it prints
nothing during 15 seconds.
$> ./b.d
dtrace: script './b.d' matched 1 probe
^C
$> cat b.d
#!/usr/sbin/dtrace -s
profile:::tick-1s
{
printf("out\n");
}
$> date;./b.d;date
Mon Jan 11 23:13:00 GMT 2010 ==> begin at 23:13:00
dtrace: script './b.d' matched 1 probe
^C
Mon Jan 11 23:13:14 GMT 2010 ==>: end at 23:13:14, so it runs for 14
seconds, but no output.
$>
$> cat /etc/release
* Solaris 10 11/06 s10x_u3wos_10 X86*
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 14 November 2006
$> uname -a
SunOS srwdb22 5.10 Generic_125101-05 i86pc i386 i86pc
Thanks,
Daniel
------------------------------------------------------------------------
_______________________________________________
dtrace-discuss mailing list
[email protected]
_______________________________________________
dtrace-discuss mailing list
[email protected]
