Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!news.cps.udayton.edu!news.engr.udayton.edu!blackbird.afit.af.mil!zombie.ncsc.mil!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Needed: Diagnosis of syslog message Date: 30 Jul 1996 21:25:58 GMT Organization: Private BSD site, Dresden Lines: 40 Message-ID: <4tlul6$c0o@uriah.heep.sax.de> References: <betts.198.294EDD70@onramp.net> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E betts@onramp.net (Jeff Betts) wrote: > Jul 28 01:29:00 rob /kernel: swap_pager: out of space > Jul 28 01:30:00 rob /kernel: pid 27208: cron: uid 0: exited on signal 11 > Jul 28 01:30:00 rob /kernel: Process 27209 killed by vm_fault -- out of swap You've got too few virtual memory. In FreeBSD, virtual memory = physical memory + swap size. So increasing either of them should help. > System is a Cyrix 486-DX2-80 w/ 16meg RAM. Swap partition (oops, is that a > slice? :-) is whatever doce recommended (RAM * 4?). (It's a swap partition, btw. :) There's nothing ``recommended'', except that i would recommend you to use as much swap as you actually need. Apparently, you've got too few right now, OTOH, much more than 4 x RAM will likely cause the machine to thrash if its really used by concurrent processes. In other words: you need more RAM if you've got too many memory-hogging processes. Of course, you could try running a ps -alx to see what the memory hogs are (the VSZ column). You can also try to reduce the default datasegment size resource limit in the kernel if you are suspecting users to run overly large processes. The predefined limit is 64 MB per process which might already be too much in your situation if there is more than one processes actually using the full amount. Alas, the option to reduce this is somewhat complicated (since it's not really intended to be an option), it is: options "DFLDSIZ='(16UL*1024*1024)'" in your kernel config file, to limit the data segment size to 16 MB. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)