On 12/15/2010 4:50 PM, James Litchfield wrote:
Try running truss first to see what you should look for - fstat64 in this
case.
I should have specified in the first post; the same dtrace works fine in the
global zone, so that's not the problem:
# dtrace -n 'syscall::stat:*' -c "ls /"
dtrace: description 'syscall::stat:*' matched 2 probes
bin etc kernel net rmdisk
shared ts-auto-pool.dat wwss
boot export lib opt root
src usr zonepool
dev home media platform rpool
system var
devices import micro proc sbin
tmp workspace
doe java mnt re scde
ts-auto-pool ws
dtrace: pid 4947 has exited
CPU ID FUNCTION:NAME
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
0 78297 stat:entry
0 78298 stat:return
-Drew
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
