Brian Candler
5/11/2007 9:05:00 AM
On Fri, May 11, 2007 at 05:56:21PM +0900, Jung wook Son wrote:
> Brian Candler wrote:
> > On Fri, May 11, 2007 at 05:25:45PM +0900, J. Wook wrote:
> >> #<Errno::EMFILE: Too many open files - socket(2)> raised.
> >
> > What does ulimit -a show? Particularly look at max open files
>
> dev@seoul$ ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> max nice (-e) 20
> file size (blocks, -f) unlimited
> pending signals (-i) unlimited
> max locked memory (kbytes, -l) unlimited
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) unlimited
> max rt priority (-r) unlimited
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) unlimited
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
Hmm. Should be enough, unless you're opening other file-like objects in your
program. But you could try raising/lowering ulimit -n to see if it makes a
difference.