Messages in this thread |  | | Date | Tue, 28 May 1996 18:22:37 -0700 (MST) | From | "Jeff Coy Jr." <> | Subject | Re: MM bug |
| |
On Tue, 28 May 1996 d-seaman@ukans.edu wrote:
=> On Mon, 27 May 1996, Alfredo Sanjuan wrote: => => > On Mon, 27 May 1996, Martin Mares wrote: => > => > > yet): You can simply crash the system by issuing "grep any_string /dev/zero". => > > As the lines in /dev/zero have infinite length, grep tries to allocate still more => > > memory for its line buffer until the memory is exhausted. But no out of memory => > > message appear and the system gets frozen (interrupts work, but normal processes => > => > Hmmm....seems to work well for me... => => Also works for me. I get a "grep: memory exhausted" error and the system => continues like normal. =>
for me, using kernel v1.99.8, libc v5.3.12, and grep v2.0, i get the message
no memory left for grep
reprinting about every 20 seconds, and although i can switch VTs, the system is utterly unusable and completely unresponsive. shift-scrllock shows no swap memory left. the only way out is to hit reset (i waited about 10 minutes).
i have 24 megs ram, with a 30 meg swap partition. 486dx2 if that helps any.
jeff --- Why Linux? source code. POSIX. tcpip. job control. support from the authors. drivers for most hardware. because one terminal or process is never enough. forget the other O/Ss, i use Linux- the choice of a GNU generation.
|  |