From: Samuel Flory <sflory@rackable.com>
To: John Coppens <jcoppens@usa.net>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: proc/sys/fs file-nr?
Date: 16 Aug 2002 15:22:27 -0700 [thread overview]
Message-ID: <1029536548.6469.185.camel@flory.corp.rackablelabs.com> (raw)
In-Reply-To: <20020816183312.728a970a.jcoppens@usa.net>
On Fri, 2002-08-16 at 14:33, John Coppens wrote:
> Hi.
>
> The last few days I had a problem with an image viewer, and thought I'd investigate
> a little. The program makes thumbnails, and after a while, complains about
> 'too many files open'. I found a reference to the proc/sys/fs/file-max and
> wanted to check file-nr first. /usr/src/linux/Documentation states:
>
> "The three values in file-nr denote the number of allocated file handles, the
> number of used file handles, and the maximum number of file handles."
>
> I'm confused now. Each time I open a new directory with images, the second number
> _decreases_! It _increases_ when I close the viewer program. Is this normal?
>
> Finally, the viewer (gThumb) gives up at:
>
> 1961 50 8192
>
> with the 'too many...' error. Shouldn't the number increase till 8192? This is
> the number in file-max? (Kernel 2.4.18)
Check inode-nr in addition to file-max. What is your ulimit set to. I
think the default is 1024.
[root@flory sflory]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 4086
virtual memory (kbytes, -v) unlimited
[root@flory sflory]# ulimit -n 2048
[root@flory sflory]# ulimit -n
2048
next prev parent reply other threads:[~2002-08-16 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 21:33 John Coppens
2002-08-16 22:22 ` Samuel Flory [this message]
2002-08-17 5:06 ` John Coppens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029536548.6469.185.camel@flory.corp.rackablelabs.com \
--to=sflory@rackable.com \
--cc=jcoppens@usa.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®