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.wildstar.net!newsfeed.direct.ca!op.net!www.nntp.primenet.com!nntp.primenet.com!feed1.news.erols.com!news From: Ken Bigelow <kbigelow@www.play-hookey.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: /kernel: file: table is full Date: Sat, 05 Oct 1996 09:47:54 +0000 Organization: Erol's Internet Services Lines: 56 Message-ID: <32562ECA.38A5@www.play-hookey.com> References: <532v4j$672@netaxs.com> Reply-To: kbigelow@www.play-hookey.com NNTP-Posting-Host: kenjb05.play-hookey.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (Win16; U) A. Karl Heller wrote: > > We just started to use a FreeBSD 2.1.5 box as a new mail hub. Our log > files soon filled up with: > > Oct 4 04:40:39 /kernel: file: table is full > Oct 4 04:40:39 last message repeated 3 times > Oct 4 04:40:39 sendmail[6157]: EAA06157: SYSERR(UID0): Can't create trans > cript file xfEAA06157: Too many open files in system > Oct 4 04:40:39 sendmail[6157]: EAA06157: SYSERR(UID0): Can't open /dev/nu > ll: Too many open files in system > Oct 4 04:40:40 /kernel: file: table is full > > Over and over again for hours. Anybody know how to tune this paramiter > to allow more open files? > > Its a custom kernel with the following options: > > cpu "I586_CPU" > maxusers 10 > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options NFS #Network Filesystem > options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 > options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device > options BOUNCE_BUFFERS #include support for DMA bounce buffers > options UCONSOLE #Allow users to grab the console > > options SYSVSHM > options SYSVSEM > options SYSVMSG > config kernel root on sd0 > > pseudo-device pty 32 > > I don't think maxusers or pty has something to do with it since there > weren't any errors about the proc table being full. This sounds more > like a file system issue. > > Any help would be appreciated. Other than that and the occasional > "Adjusting time too_old" ( or some such message, what is that? ) the > system is rock stable. Great job! > The proc table is not the only table set by maxusers. Try cranking it up to around 40 and see what happens. Then you can concern yourself with the number of processes any one user may need to have. -- Ken Are you interested in | byte-sized education | http://www.play-hookey.com over the Internet? |