Date: Tue, 29 Feb 2000 11:38:53 -0500 (EST) From: Vivek Khera <khera@kciLink.com> To: "Sean O'Connell" <sean@stat.Duke.EDU> Cc: FreeBSD-STABLE <stable@FreeBSD.ORG> Subject: Re: Error: "Maximum file descriptors exceeded"... Message-ID: <14523.63005.58024.976749@onceler.kcilink.com> In-Reply-To: <20000229113443.F21891@stat.Duke.EDU> References: <Pine.BSF.4.21.0002291045580.58885-100000@epsilon.lucida.qc.ca> <v0422080ab4e19df0856e@[195.238.1.121]> <38BBF0D3.6ED0DFD3@thehousleys.net> <20000229113443.F21891@stat.Duke.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "SO" == Sean O'Connell <sean@stat.Duke.EDU> writes: SO> I thought this too, but if I run SO> sysctl -w kern.maxfiles=4096 SO> sysctl -w kern.maxfilesperproc=4096 SO> Now: SO> % sysctl kern.maxfiles SO> kern.maxfiles: 4096 SO> % sysctl kern.maxfilesperproc SO> kern.maxfilesperproc: 4096 SO> However, limit -h (tcsh builtin) and limits -H still report SO> descriptors 2088 SO> openfiles 2088 [ ... ] SO> Am I missing something obvious? Are these values really updated? Did you logout and back in? I don't think upping the system-wide limits will dynamically update the limits given to processes that are already started. Logging in again will cause your process (ie, the shell) to have its resource limits set to the current hard limits. ps: Go Duke!!! I really miss the place. ;-( -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14523.63005.58024.976749>