Hello experts,
Is there a way to find which program is changing the symlink for a
particular slice using dtrace?
Basically, I have following problem:
While doing live upgrade (luupgrade script), the symbolic link for a
particular slice (c1d0s4 which gets mounted on /a during luupgrade) is
All,
from reading of the DTrace documentation, eg. at
http://wikis.sun.com/display/DTrace/pid+Provider, I got the impression that
I could do something like
dtrace -n 'pid$target:mylib::entry{}' -c ...
for any existing mylib.so{.1} ... which does not seem to be the case; for
the
On 04/01/09 22:11, Michael Schuster wrote:
All,
from reading of the DTrace documentation, eg. at
http://wikis.sun.com/display/DTrace/pid+Provider, I got the impression
that I could do something like
dtrace -n 'pid$target:mylib::entry{}' -c ...
for any existing mylib.so{.1} ... which
On Wed, Apr 1, 2009 at 12:41 PM, Michael Schuster
michael.schus...@sun.com wrote:
All,
from reading of the DTrace documentation, eg. at
http://wikis.sun.com/display/DTrace/pid+Provider, I got the impression that
I could do something like
dtrace -n 'pid$target:mylib::entry{}' -c ...
Hello Nishchaya,
Wednesday, April 1, 2009, 10:22:53 AM, you wrote:
NB Hello experts,
NB Is there a way to find which program is changing the symlink for a
NB particular slice using dtrace?
I guess it is probably devfsadmd who is changing your symlink.
If you want to trace what's touching
On 04/01/09 10:06, Chad Mynhier wrote:
On Wed, Apr 1, 2009 at 12:41 PM, Michael Schuster
michael.schus...@sun.com wrote:
All,
from reading of the DTrace documentation, eg. at
http://wikis.sun.com/display/DTrace/pid+Provider, I got the impression that
I could do something like
dtrace -n
On Wed, Apr 1, 2009 at 1:42 PM, Michael Schuster
michael.schus...@sun.com wrote:
I see similar stuff for my library ... so why would dtrace fail to show
calls into libdladm for a process that's started by dtrace (ie using -c)
(using -Z as someone suggested)
$ dtrace -Z -n
On Wed, Apr 1, 2009 at 4:02 PM, Steve Scargall steve.scarg...@sun.com wrote:
As Pavan suggested DTrace isn't preloading the libraries. Try using the
LD_PRELOAD, LD_PRELOAD_32, or LD_PRELOAD_64 environmental variables to
preload the libraries you need. There's an example on my blog
Andrew,
As I understand it, the direct calls to routines in libdtrace.so are
considered unstable and not for public consumption. However, there is
an approved Java API, and a person who has documented libdtrace.so so
that others can use it. (He documented it for use with TCL, but I think
it
