[...]
To get around the problem
pmap: cannot examine 5608: address space is
changing
and get a closer look, try stopping the process
first:
pstop 5608
and then running pmap or whatever to inspect it,
and finally running
prun 5608
to let it run again.
Why is pmap not
Richard L. Hamilton wrote:
[...]
To get around the problem
pmap: cannot examine 5608: address space is
changing
and get a closer look, try stopping the process
first:
pstop 5608
and then running pmap or whatever to inspect it,
and finally running
prun 5608
to let it run again.
Why is
A 32-bit process _can't_* be bigger than 4GB, and as far as the kernel
is concerned, AFAIK won't be bigger than 2GB in terms of regular memory
(although it could have a frame buffer or something mapped in the
part of the address space reserved for I/O devices, making its total
size perhaps appear
On Sun, Apr 25, 2010 at 8:43 AM, Richard L. Hamilton rlha...@smart.net wrote:
[...]
To get around the problem
pmap: cannot examine 5608: address space is
changing
and get a closer look, try stopping the process
first:
pstop 5608
and then running pmap or whatever to inspect it,
[...]
Recent ksh93 has a lot of built-in commands that
used to require
running external programs.
Is there any documentation about this feature?
The ksh93 man page includes some (but perhaps not all) information about builtin
commands.
The ksh93 built-in command builtin will list all
Good Day all; I'm new here.
We have an urgent problem. A test server which is ready for
demonstration (and purchase from Sun/Oracle) suffers from some kind of
kernel problem: A 32bit process (ksh) started to consume more than 4G
of memory and is still running but defeats some attempts to observe
On Sun, Apr 25, 2010 at 1:39 AM, Yves Huang
yves.huang.proje...@googlemail.com wrote:
Good Day all; I'm new here.
We have an urgent problem. A test server which is ready for
demonstration (and purchase from Sun/Oracle) suffers from some kind of
kernel problem: A 32bit process (ksh) started to
A 32-bit process _can't_* be bigger than 4GB, and as far as the kernel
is concerned, AFAIK won't be bigger than 2GB in terms of regular memory
(although it could have a frame buffer or something mapped in the
part of the address space reserved for I/O devices, making its total
size perhaps appear
(oops, got chopped in the forum the first time, due to punctuation it didn't
like)
A 32-bit process _can't_* be bigger than 4GB, and as far as the kernel
is concerned, AFAIK won't be bigger than 2GB in terms of regular memory
(although it could have a frame buffer or something mapped in the
part
On Sun, Apr 25, 2010 at 6:08 AM, Richard L. Hamilton rlha...@smart.net wrote:
A 32-bit process _can't_* be bigger than 4GB, and as far as the kernel
is concerned, AFAIK won't be bigger than 2GB in terms of regular memory
(although it could have a frame buffer or something mapped in the
part of
10 matches
Mail list logo
