Date: Thu, 21 Jan 2016 19:44:01 +0000 From: "Batutis, Ed" <Ed.Batutis@netapp.com> To: Mateusz Guzik <mjguzik@gmail.com> Cc: Joerg Sonnenberger <joerg@britannica.bec.de>, Diane Bruce <db@db.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: RE: get number of open files in a process? Message-ID: <31126442b7d347c5976a57aabc2e5792@hioexcmbx08-prd.hq.netapp.com> In-Reply-To: <20160121191308.GA21869@dft-labs.eu> References: <ea9f2ab2d4f543c8ad34fdeb082f8c7a@hioexcmbx08-prd.hq.netapp.com> <20160121153636.GA10961@britannica.bec.de> <20160121161637.GA83843@night.db.net> <20160121162527.GA11600@britannica.bec.de> <d26cc2fcea304ea6a89f61c2ec497322@hioexcmbx08-prd.hq.netapp.com> <20160121191308.GA21869@dft-labs.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > However, the real question is what do you need this for. > I would like to know when I am getting close to hitting the file handle limit. This is useful for two reasons: 1) if I run out of available file handles this will most likely cause my process to crash. If I start logging when the count begins to get dangerously high, then I might after the fact be able to determine what was going on to cause that. 2) Some handles are used by a user interface. It would be nice if the server could reject connections when the open handle count hit a critical threshold so the user interface doesn't become part of the problem - obscuring the actual underlying cause. Thanks, =Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31126442b7d347c5976a57aabc2e5792>