perhaps it should. by default mac os x shows:

bash-> ulimit -a
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) 6144
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 256
pipe size          (512 bytes, -p) 1
stack size            (kbytes, -s) 512
cpu time             (seconds, -t) unlimited
max user processes            (-u) 100
virtual memory        (kbytes, -v) 6656

while linux (redhat 7.1) shows:

bash-> ulimit -a
core file size (blocks)     1000000
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          12275
virtual memory (kbytes)     unlimited

apparently there are more default limitations imposed by the OS on mac os x than on linux -- anyone else ever seen the "too many open files" error on a different platform? what are the constraints imposed by windows?

--bill

On Tuesday, August 19, 2003, at 05:36 PM, Conal Tuohy wrote:

Bill French wrote:

i've been working for a while trying to find the source of a
nasty "too
many open files" error when building lucene indexes using cocoon's
LuceneIndexTransformer on mac os x.  just for kicks, i decided to try
everything out on a linux machine and didn't have any problems, and
realized that it was an OS-specific thing. after some googling, i
discovered that "a java application can't have more than 256
files open
at once on mac os x."

read more: http://www.amug.org/~glguerin/howto/More-open-files.html

i'd be happy to make a note in the LuceneIndexTransformer wiki about
this, if anyone else thinks it's worthwhile.

Absolutely! Please do ... and good on you for spotting the problem!


But maybe this should go in the standard shell script for running Cocoon?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to