[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19991202: Thoughts on Nmap and number of files in a directory

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19991202: Thoughts on Nmap and number of files in a directory
  • Date: Thu, 2 Dec 1999 10:56:21 -0700
I have run into problems with nmap where I exceed the maximum
number of files in the data directory.

FL_MFIL has the maximum number of files(300) hardcoded.
Also, FL_SCND called by FL_MFIL is hardcoded with
the size of the filnam string (12801) in 2 places.
These sizes might be good candidates for the gemprm.prm
file.

More importantly, there is currently no error check in
those routines which prevents a messy crash when
CFL_SCND returns more than 300 file names in the string.
If the sizes were defined in the include files, then
FL_SCND would only need to check if nf > maxfilenames
and create an error message, or truncate the list
as appropriate.

Steve Chiswell
Unidata User Support