Date: Sat, 29 Jan 2000 20:29:50 -0800 From: "Jay Krell" <jay.krell@cornell.edu> To: <questions@freebsd.org> Subject: Re: "too many files open"? Message-ID: <006a01bf6ada$a7071fe0$8101a8c0@jayk-home4nt>
next in thread | raw e-mail | index | archive | help
Well.. the network on this machine is incompletely configured, but Samba is installed. I found that there were lots of nmbd processes running. I commented out the appro lines in inetd.conf. This might explain the "too many open files". Building Code Crusader (and Gwydion Dylan 2.x) still takes hours -- more than eight running them concurrently. I'm reinstalling with a seperate 100meg /var (I coulldn't cd /var ; mv * /usr/var) and will link /tmp to /usr/tmp.. If this still doesn't work, I'll find another home for the 2gig fat and go closer to a "dangerously dedicated" hard drive.. ..Jay -----Original Message----- From: Jay Krell <jay.krell@cornell.edu> To: questions@freebsd.org <questions@freebsd.org> Date: Saturday, January 29, 2000 2:48 AM Subject: "too many files open"? >Has anyone seen a BSD ~3.4 install where > >1) building /usr/ports/devel/codecrusader is amazingly slow > The system is a 450MHz Pentium II with 128megs; I didn't > notice this on a 200MHz Pentium Pro with 128megs >2) trying to do something like concurrently build codecrusader > and the kernel (or maybe it was only make depend on the kernel) > produces the error "too many open files" upon which basically > nothing works (until a reboot) -- running top reports that > /usr/lib/termmap.so.2 doesn't exist, running ls reports "too many > open files in system", and so does ps, dmesg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006a01bf6ada$a7071fe0$8101a8c0>