Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!usenet.ins.cwru.edu!odin!chet From: chet@odin.ins.cwru.edu (Chet Ramey) Newsgroups: comp.os.386bsd.bugs Subject: Re: VM problems w/unlimited memory? Date: 15 Mar 1993 23:26:53 GMT Organization: Case Western Reserve University, Cleveland OH (USA) Lines: 18 Message-ID: <1o33btINNqoa@usenet.INS.CWRU.Edu> References: <C3qpIH.Is9@unx.sas.com> <1993Mar15.220646.9854@fcom.cc.utah.edu> NNTP-Posting-Host: odin.ins.cwru.edu In article <1993Mar15.220646.9854@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >This is obviously a problem in the open code. bash is stupid and doesn't >just ask the system how many files it can open and assume all the ones >that are supposed to be are closed; this results in overruning the process >file table in the kernel, triggering a kernel bug. Please don't say stupid things like this without checking them first. There is no code in bash that says `close every fd from 3 to getdtablesize()'. Bash has some speed problems, but closing file descriptors indiscriminately is not one of them. Chet -- ``The use of history as therapy means the corruption of history as history.'' -- Arthur Schlesinger Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu