Hi Experts,
I wanna know why truss makes the process running slow when we run truss on
that,why not the same with the dtrace?
Thanks,
Pradeep
___
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinf
Thanks a lot!! It worked.
I was able to get dev link name from the physical paths for all the SD nodes
and then filter out the ones that I was interested in.
However if I have a large number of luns say more than 5000, then is there more
efficient way in libdevinfo to find out dev link names for
On Mon, Aug 24, 2009 at 08:16:42PM +1000, Gavin Maltby wrote:
> Hi
>
> Ian Collins wrote:
> >I'm looking for pointers towards kernel memory debug code.
> >
> >I had a system that periodically ran out of physical memory and froze.
> >It turns out the system had kmem_flags of 0xf and
> >kmem_bufc
On Mon, Aug 24, 2009 at 3:23 PM, Darren J Moffat wrote:
> Vincent Torri wrote:
>
>> Hey,
>>
>> I would like to know how I can notify the file system on OpenSolaris. The
>> low level API on linux is Inotify (it's a kernel module), and on Windows, it
>> is ReadDirectoryChangeW||. Which one is it wit
Vincent Torri wrote:
Hey,
I would like to know how I can notify the file system on OpenSolaris.
The low level API on linux is Inotify (it's a kernel module), and on
Windows, it is ReadDirectoryChangeW||. Which one is it with OpenSolaris ?
You need to use the port event system.
See port_crea
Vincent Torri wrote:
> I would like to know how I can notify the file system on OpenSolaris.
> The low level API on linux is Inotify (it's a kernel module), and on
> Windows, it is ReadDirectoryChangeW||. Which one is it with OpenSolaris ?
OpenSolaris has FAM and the 'port' feature to allow for no
Hey,
I would like to know how I can notify the file system on OpenSolaris. The
low level API on linux is Inotify (it's a kernel module), and on Windows, it
is ReadDirectoryChangeW. Which one is it with OpenSolaris ?
thank you
Vincent Torri
___
opensola
On Mon, 24 Aug 2009 04:04:35 -0700 (PDT)
damitri wrote:
> Hello All,
>
> How can I get disk’s dev link name (which is in the form /dev/dsk/CxTyDz)
> from libdevinfo if I have its corresponding physical path?
>
> Eg: When I do “ls -l /dev/dsk/c1t0d0s0” the output is
>
> # ls -l /dev/dsk/c1t0d0
Hello All,
How can I get disk’s dev link name (which is in the form /dev/dsk/CxTyDz) from
libdevinfo if I have its corresponding physical path?
Eg: When I do “ls -l /dev/dsk/c1t0d0s0” the output is
# ls -l /dev/dsk/c1t0d0s0
lrwxrwxrwx 1 root root 43 Jun 3 16:32 /dev/dsk/c1t0d0s0
Hi
Ian Collins wrote:
I'm looking for pointers towards kernel memory debug code.
I had a system that periodically ran out of physical memory and froze.
It turns out the system had kmem_flags of 0xf and
kmem_bufctl_audit_cache usage was getting to about 1.3GB. I'm
interested is seeing how t
10 matches
Mail list logo