On Mon, Dec 09, 2002 at 08:28:22PM +0100, Bernhard Reiter wrote:
On Mon, Dec 09, 2002 at 02:13:36PM -0500, Kevin Slover wrote:
> Just a quickie...
> is there a reason why r.patch is limited to only 200 files at a time?
> First time that I have ever noticed this...(first time I have ever done
> more than 200 files!!). Anyway to get around this without chopping up
> the data? Thanks!
On Tue, Dec 10, 2002 at 10:52:00AM +0100, Markus Neteler wrote:
... taken here from "grasslist"....
On Mon, Dec 09, 2002 at 08:28:22PM +0100, Bernhard Reiter wrote:
> On Mon, Dec 09, 2002 at 02:13:36PM -0500, Kevin Slover wrote:
> > Just a quickie...
> > is there a reason why r.patch is limited to only 200 files at a time?
> > First time that I have ever noticed this...(first time I have ever done
> > more than 200 files!!). Anyway to get around this without chopping up
> > the data? Thanks!
>
> Check out
> http://freegis.org/cgi-bin/viewcvs.cgi/grass/src/raster/r.patch/cmd/nfiles.h?rev=1.3&content-type=text/vnd.viewcvs-markup
>
> Most operating system limit the number of open files.
> If yours can more than 250, just raise that number and recompile.
Is there any (UN*X) system variable describing this? Then we could
perhaps add a MAXFILEOPEN or similar to src/include/gis.h.
Someone more familiar with posix should answer this.
There is OPEN_MAX and FOPEN_MAX for some Linux kernels.
In any case we should also substract a good number (like 50) from this.
So 200 is a good number unless you build an optimised binary.