On Jan 15, 2008 4:43 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Aubrey Li wrote:
> > On Jan 15, 2008 2:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> >> Hi Aubrey,
> >>
> >>> ---snip--
> >>> setrlimit(RLIMIT_NOFILE, 0xFD7FFFDFEE80)= 0
> >>> openat(AT_FDCWD, "/
Aubrey Li wrote:
> On Jan 15, 2008 2:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>> Hi Aubrey,
>>
>>> ---snip--
>>> setrlimit(RLIMIT_NOFILE, 0xFD7FFFDFEE80)= 0
>>> openat(AT_FDCWD, "/dev/dtrace/provider", O_RDONLY|O_NDELAY|O_LARGEFILE) = 3
>>> fcntl(3, F_SETFD,
On Jan 15, 2008 2:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi Aubrey,
>> ---snip--
> > setrlimit(RLIMIT_NOFILE, 0xFD7FFFDFEE80)= 0
> > openat(AT_FDCWD, "/dev/dtrace/provider", O_RDONLY|O_NDELAY|O_LARGEFILE) = 3
> > fcntl(3, F_SETFD, 0x0001) = 0
Hi Aubrey,
Aubrey Li wrote:
> Sorry for the delay(time difference). Now I got more details.
> # truss dtrace -l
> snip
> mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0xFD7FFF18
> mmap(0x0001, 24576, PROT_READ|PROT_WRITE|PROT_EXE
Hi Aubrey,
Aubrey Li wrote:
> Sorry for the delay(time difference). Now I got more details.
> # truss dtrace -l
> snip
> mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0xFD7FFF18
> mmap(0x0001, 24576, PROT_READ|PROT_WRITE|PROT_EX
Sorry for the delay(time difference). Now I got more details.
# truss dtrace -l
snip
mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0xFD7FFF18
mmap(0x0001, 24576, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0
On Jan 15, 2008 12:44 AM, Adam Leventhal <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 14, 2008 at 12:52:55PM +, Sean McGrath - Sun Microsystems
> Ireland wrote:
> > Aubrey Li stated:
> > < Every first time to run dtrace command after the system boot up,
> > < It takes a very long time to get respo
On Jan 14, 2008 10:46 PM, Bryan Cantrill <[EMAIL PROTECTED]> wrote:
>
> On Mon, Jan 14, 2008 at 09:16:34PM +0800, Aubrey Li wrote:
> > On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
> > <[EMAIL PROTECTED]> wrote:
> > > Aubrey Li stated:
> > > < Every first time to run dtrace comma
Hi James,
James C. McPherson wrote:
> Aubrey Li wrote:
>
>> On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Aubrey Li stated:
>>> < Every first time to run dtrace command after the system boot up,
>>> < It takes a very long time to get r
On Mon, Jan 14, 2008 at 06:46:49AM -0800, Bryan Cantrill wrote:
> > So, I failed to understand the modules loading needs 4 minutes.
>
> Yes, this is definitely fishy. Is this a highly memory constrained system?
> If you "modunload -i 0" enough times to get dtrace(7D) unloaded (that
> is, "dtrace"
On Mon, Jan 14, 2008 at 12:52:55PM +, Sean McGrath - Sun Microsystems
Ireland wrote:
> Aubrey Li stated:
> < Every first time to run dtrace command after the system boot up,
> < It takes a very long time to get response.
> < But the second time is OK, as follows:
> <
> < # time dtrace -l > /d
On Mon, Jan 14, 2008 at 09:16:34PM +0800, Aubrey Li wrote:
> On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
> <[EMAIL PROTECTED]> wrote:
> > Aubrey Li stated:
> > < Every first time to run dtrace command after the system boot up,
> > < It takes a very long time to get response.
>
On Jan 14, 2008 9:38 PM, James C. McPherson <[EMAIL PROTECTED]> wrote:
> Aubrey Li wrote:
> > On Jan 14, 2008 9:26 PM, Aubrey Li <[EMAIL PROTECTED]> wrote:
> >> On Jan 14, 2008 9:22 PM, James C. McPherson <[EMAIL PROTECTED]> wrote:
>
> >>> If you run "dtrace -l" with no args, *every* single lo
Aubrey Li wrote:
> On Jan 14, 2008 9:26 PM, Aubrey Li <[EMAIL PROTECTED]> wrote:
>> On Jan 14, 2008 9:22 PM, James C. McPherson <[EMAIL PROTECTED]> wrote:
>>> If you run "dtrace -l" with no args, *every* single loadable
>>> module on the system will be loaded, interrogated by dtrace
>>> and th
Hi James,
James C. McPherson wrote:
> Aubrey Li wrote:
>
>> On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Aubrey Li stated:
>>> < Every first time to run dtrace command after the system boot up,
>>> < It takes a very long time to get
On Jan 14, 2008 9:26 PM, Aubrey Li <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2008 9:22 PM, James C. McPherson <[EMAIL PROTECTED]> wrote:
> > Aubrey Li wrote:
> > > On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
> > > <[EMAIL PROTECTED]> wrote:
> > >> Aubrey Li stated:
> > >> < Eve
On Jan 14, 2008 9:22 PM, James C. McPherson <[EMAIL PROTECTED]> wrote:
> Aubrey Li wrote:
> > On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
> > <[EMAIL PROTECTED]> wrote:
> >> Aubrey Li stated:
> >> < Every first time to run dtrace command after the system boot up,
> >> < It take
Aubrey Li wrote:
> On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
> <[EMAIL PROTECTED]> wrote:
>> Aubrey Li stated:
>> < Every first time to run dtrace command after the system boot up,
>> < It takes a very long time to get response.
>> < But the second time is OK, as follows:
>>
On Jan 14, 2008 8:52 PM, Sean McGrath - Sun Microsystems Ireland
<[EMAIL PROTECTED]> wrote:
> Aubrey Li stated:
> < Every first time to run dtrace command after the system boot up,
> < It takes a very long time to get response.
> < But the second time is OK, as follows:
> <
> < # time dtrace -l > /
Aubrey Li stated:
< Every first time to run dtrace command after the system boot up,
< It takes a very long time to get response.
< But the second time is OK, as follows:
<
< # time dtrace -l > /dev/null
<
< real4m8.011s
< user0m0.116s
< sys 0m2.420s
This first time is probably whe
20 matches
Mail list logo
