Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6697 ; Tue, 12 Jan 93 08:08:14 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!spool.mu.edu!uwm.edu!linac!att!mcdchg!chinet!randy From: randy@chinet.chi.il.us (Randy Suess) Subject: Re: [386BSD] Here is the answer, Re: out of mem Message-ID: <C0ux12.9zn@chinet.chi.il.us> Organization: Chinet - Public Access UNIX References: <C0Frt6.2wq@chinet.chi.il.us> <1993Jan12.151341.24515@data-io.com> <C0t6r1.6KD@NeoSoft.com> Date: Thu, 14 Jan 1993 18:36:37 GMT Lines: 19 In article <C0t6r1.6KD@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes: >In article <1993Jan12.151341.24515@data-io.com> bachesta@pugsley.Data-IO.COM (Jim Bachesta) writes: >>I have been following the response on your posting. It seems that people have >>gone off on the wrong tangent on ulimit. I have seen this problem with virtual >>memory. I have 10 Megs of Ram and 30 Megs of swap. I am unable to compile motif >>I am sure it has nothing to do with the ulimit. >With bash on Berkeley the ulimit command does much more than set the max >size of a disk file. Sigh. This is not a ulimit problem. All shells have been tried (/bin/sh is bourne shell, correct?) including real ksh setting all possible parameters at highest level. Problem still occurs. This makes 386bsd unusable. It does amaze me however that no one else seems to have this problem. -- I am created Shiva the Destroyer; Death, the shatterer of worlds! Who is this dog meat who stands before me now? That's the biz, sweetheart. Randy Suess randy@chinet.chi.il.us