Re: 4096 byte limit to /proc/PID/environ ?

Followup to:  <[email protected]>
By author:    James Pearson <[email protected]>
In newsgroup: linux.dev.kernel
> 
> 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 ...
> 

Funny enough, I was looking at this yesterday.  I think there is a
pretty clean solution for it, I just haven't had a chance to attack it
yet.

	-hpa

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • 4096 byte limit to /proc/PID/environ ?
    • From: James Pearson <[email protected]>
  • Re: 4096 byte limit to /proc/PID/environ ?
    • From: "linux-os \(Dick Johnson\)" <[email protected]>
  • Re: 4096 byte limit to /proc/PID/environ ?
    • From: James Pearson <[email protected]>

• Prev by Date: Re: [PATCH] updated reiser4 - reduced cpu usage for writes by writing more than 4k at a time (has implications for generic write code and eventually for the IO layer)
• Next by Date: Re: [PATCH] updated reiser4 - reduced cpu usage for writes by writing more than 4k at a time (has implications for generic write code and eventually for the IO layer)
• Previous by thread: Re: 4096 byte limit to /proc/PID/environ ?
• Next by thread: Re: 4096 byte limit to /proc/PID/environ ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]