I'm getting an odd behavior while trying to trace a mysql process using
the -p flag on a Sun Cluster.
This fails
# dtrace -n 'pid$target::*mysql_parse*:entry {}' -p `pgrep -x mysqld`
dtrace: failed to grab pid 16537: process is traced
Yet this works
# dtrace -n 'pid$1::*mysql_parse*:entry {}' `pgrep -x mysqld`
dtrace: description 'pid$1::*mysql_parse*:entry ' matched 1 probe
All processes managed within the Sun Cluster agent framework appear to
exhibit this behavior yet if they aren't managed by cluster they appear
to work. Has anyone seen this problem? Also any pointers to investigate
this further?
# uname -a
SunOS wolverine 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire
Thanks
Dave
_______________________________________________
dtrace-discuss mailing list
[email protected]
