Re: Two 2.0.10 problems?

Matthias Urlichs (smurf@smurf.noris.de)
Wed, 7 Aug 1996 11:27:19 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Eric W. Biederman: "Re: Problems with"
Previous message: Al Longyear: "Re: proc fs and shared pids"
Maybe in reply to: Joe Fouche: "Two 2.0.10 problems?"

In linux.dev.kernel, article <199608062017.WAA12064@informatik.uni-koblenz.de>,
Systemkennung Linux <linux@mailhost.uni-koblenz.de> writes:
>
> Less tries to hold the entire data in memory when reading from a pipe.
> In your case thsi were several megabytes and your system was simply
> heavily swapping.
>
This can be blocked with the -B abd -b flags (RTFM).

A more serious issue is the fact that /proc/kcore contains all of main
memory, including the I/O address space above 640k. It might be harmful to
randomly read from these addresses...

-- Forgetfulness, n.: A gift of God bestowed upon debtors in compensation for their destitution of conscience.

-- 
Matthias Urlichs         \  noris network GmbH  /  Xlink-POP Nürnberg 
Schleiermacherstraße 12   \   Linux+Internet   /   EMail: urlichs@noris.de
90491 Nürnberg (Germany)   \    Consulting+Programming+Networking+etc'ing
   PGP: 1024/4F578875   1B 89 E2 1C 43 EA 80 44  15 D2 29 CF C6 C7 E0 DE
       Click <A HREF="http://info.noris.de/~smurf/finger">here</A>.    42

Next message: Eric W. Biederman: "Re: Problems with"
Previous message: Al Longyear: "Re: proc fs and shared pids"
Maybe in reply to: Joe Fouche: "Two 2.0.10 problems?"