On Wed, 9 Jan 2002, Behdad Esfahbod wrote:
>
> And why do you think process 555 exists?
Because it's in the /proc directory, and ps shows it.
>
> Does the /proc/self/mem cause the same problem too?
Yes.
>
> On Wed, 9 Jan 2002, Efraim Yawitz wrote:
>
> > What I've been doing is something lik
And why do you think process 555 exists?
Does the /proc/self/mem cause the same problem too?
On Wed, 9 Jan 2002, Efraim Yawitz wrote:
> What I've been doing is something like 'cat /proc/555/mem' with the
> problems mentioned.
>
> On Tue, 8 Jan 2002, Behdad Esfahbod wrote:
>
> >
> > Where do
What I've been doing is something like 'cat /proc/555/mem' with the
problems mentioned.
On Tue, 8 Jan 2002, Behdad Esfahbod wrote:
>
> Where do you look for them? there is useful information in /proc/self
> directory, "man proc" for what is there.
>
> On Tue, 8 Jan 2002, Efraim Yawitz wrote:
Where do you look for them? there is useful information in /proc/self
directory, "man proc" for what is there.
On Tue, 8 Jan 2002, Efraim Yawitz wrote:
> As far as I understand from /usr/src/linux/Documentation/proc.txt, the
> 'mem' files in the directories under /proc are supposed to provide
As far as I understand from /usr/src/linux/Documentation/proc.txt, the
'mem' files in the directories under /proc are supposed to provide some
kind of direct view of the memory of a process. If so, why do I see
nothing in them (as root, as the owner of the process I just get 'no such
process'.)
