dtrace discuss - Apr 2009 - tracing change in symlink?

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 
getting changed. Although luupgrade script is not supposed to change this.

This is how it looked like for sometime when luupgrade was running:

[nb229787 at va64-x2100a-sca11 ~]$ /bin/ls -l   /a/dev/dsk/c1d0s4
lrwxrwxrwx   1 root     root          48 Mar 30 03:36 /a/dev/dsk/c1d0s4 
-> ../../devices/pci at 0,0/pci-ide at 7/ide at 0/cmdk at 0,0:e

After few minutes, it got changed (the luupgrade was still running)

[nb229787 at va64-x2100a-sca11 ~]$ /bin/ls -l   /a/dev/dsk/c1d0s4
lrwxrwxrwx   1 root     other         47 Mar 30 05:10 /a/dev/dsk/c1d0s4 
-> ../../devices/pci at 0,0/pci108e,5348 at 7/disk at 0,0:e

This results in setting up the incorrect bootpath in bootenv.rc

Any pointers/help is greatly appreciated.

Thanks in advance,
Nishchaya

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 this particular link try to trace
syscalls like: open*(), unlink(), rename(), *stat*() and use a
predicate to specify path to your symlink.



-- 
Best regards,
 Robert Milkowski
                                       http://milek.blogspot.com

Thanks Robert for the pointers.

I shall definitely do that.

Regards,
Nishchaya

Robert Milkowski wrote:
> 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 this particular link try to
trace
> syscalls like: open*(), unlink(), rename(), *stat*() and use a
> predicate to specify path to your symlink.
>
>
>
>