Messages in this thread | | | Date | Sat, 17 Aug 2002 02:06:14 -0300 | From | John Coppens <> | Subject | Re: proc/sys/fs file-nr? |
| |
On 16 Aug 2002 15:22:27 -0700 Samuel Flory <sflory@rackable.com> wrote:
> > Check inode-nr in addition to file-max. What is your ulimit set to. I > think the default is 1024. > core file size (blocks) 0 data seg size (kbytes) unlimited file size (blocks) unlimited max locked memory (kbytes) unlimited max memory size (kbytes) unlimited open files 1024 pipe size (512 bytes) 8 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 2047 virtual memory (kbytes) unlimited
Ok. I suppose open files is the limit, but the problem appears much before that. Anyway, I tried to change with ulimit -n 2048, but the gThumb still gives up. (there are only 900 images in the directory, and the program gives up at maybe 600).
The numbers in /proc/sys/fs/file-nr change with a rate of about 3 - 4 each thumbnail that is opened.
John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |