public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4096 byte limit to /proc/PID/environ ?
Date: Wed, 24 May 2006 17:59:27 +0100	[thread overview]
Message-ID: <447490EF.8010000@moving-picture.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605241235110.2450@chaos.analogic.com>

linux-os (Dick Johnson) wrote:
> On Wed, 24 May 2006, James Pearson wrote:
> 
> 
>>It appears that /proc/PID/environ only returns the first 4096 bytes of a
>>processes' environment.
>>
>>Is there any other way via userland to get the whole environment for a
>>process?
>>
>>Thanks
>>
>>James Pearson
> 
> 
> 
> I think that /proc/PID/environ just returns the environment that
> existed when the process was created, irrespective of size. You
> can check this as:
> 
> #include <stdio.h>
> 
> main()
> {
>      setenv("FOO=", "1234", 1);
>      printf("%d\n", getpid());
>      pause();
> }
> 
> Variable "FOO" will not appear in /proc. It you set the environment
> in non-standard ways, overwriting the original, you can see it in
> /proc.

I'm not worried about that - more the fact that when I do:

% cat /proc/$$/environ | wc -c
4096
% env | wc -c
7329

/proc/PID/environ is truncated ...

James Pearson

  reply	other threads:[~2006-05-24 16:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 15:54 4096 byte limit to /proc/PID/environ ? James Pearson
2006-05-24 16:46 ` linux-os (Dick Johnson)
2006-05-24 16:59   ` James Pearson [this message]
2006-05-24 17:56     ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2006-05-24 19:45 James Pearson
2006-05-24 20:29 ` H. Peter Anvin
     [not found] ` <200605242029.k4OKTn9C031700@terminus.zytor.com>
2006-06-01 14:11   ` James Pearson
2007-08-15 16:54     ` Guy Streeter
2007-08-15 17:25       ` H. Peter Anvin
2007-08-21 14:40         ` Guy Streeter
2007-08-30 13:53         ` James Pearson
2007-09-03  8:17           ` Anton Arapov
2007-09-05  7:49           ` Anton Arapov
2007-09-05  7:58             ` H. Peter Anvin
2007-09-05 17:00               ` James Pearson
2007-09-05 17:18                 ` Randy Dunlap
2007-09-06  9:23                   ` James Pearson
2007-09-05 17:22                 ` Alexey Dobriyan
2007-09-06  9:31                   ` James Pearson
2007-09-06 12:31                 ` Jan Engelhardt
2007-09-06 12:34                   ` H. Peter Anvin
2007-09-06 12:34                   ` Anton Arapov
2007-09-06 16:38 James Pearson
2007-09-18 14:09 ` Anton Arapov
2007-09-18 17:09   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447490EF.8010000@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox