summary refs log tree commit diff
path: root/FAQ
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-11-25 15:42:34 +0000
committerUlrich Drepper <drepper@redhat.com>1998-11-25 15:42:34 +0000
commit0155a7737f5653e07015421b962b70fd8831c4ad (patch)
tree48ce04644835332f6d81ed848d8ff68f6d3973c9 /FAQ
parente66b6eca3d51457a2348d4dd23638a7b339b9e03 (diff)
downloadglibc-0155a7737f5653e07015421b962b70fd8831c4ad.tar.gz
glibc-0155a7737f5653e07015421b962b70fd8831c4ad.tar.xz
glibc-0155a7737f5653e07015421b962b70fd8831c4ad.zip
Update.
1998-11-25  Ulrich Drepper  <drepper@cygnus.com>

	* version.h (VERSION): Bump to 2.0.104.

1998-11-25  Mark Kettenis  <kettenis@phys.uva.nl>

	* libio/bits/stdio.h (fread_unlocked): Add missing parentheses
	around parameter n.

1998-11-24  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* time/tzfile.c (__tzfile_read): Fix comment.

1998-11-24  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* Makerules (build-shlib): Pass -O1 down to linker to get
	optimized shared libraries.

1998-11-24  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* Makeconfig ($(common-objpfx)sysd-dirs): Cope with no Subdirs
	file.  Strip "-" from inhibited subdir name.  Combine into a
	single awk program.
	($(common-objpfx)sysd-sorted): Fix sed command.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ28
1 files changed, 28 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index a3fdddee52..a3d3b5a152 100644
--- a/FAQ
+++ b/FAQ
@@ -93,6 +93,7 @@ please let me know.
 2.23.	I just upgraded my Linux system to glibc and now I get
 	errors whenever I try to link any program.
 2.24.	When I use nscd the machine freezes.
+2.25.	I need lots of open files.  What do I have to do?
 
 3. Source and binary incompatibilities, and what to do about them
 
@@ -943,6 +944,33 @@ If you need nscd, you have to use a 2.1 kernel.
 
 Note that I have at this point no information about any other platform.
 
+
+2.25.	I need lots of open files.  What do I have to do?
+
+{AJ} This is at first a kernel issue.  The kernel defines limits with
+OPEN_MAX the number of simultaneous open files and with FD_SETSIZE the
+number of used file descriptors.  You need to change these values in your
+kernel and recompile the kernel so that the kernel allows to use more open
+files.  You don't necessarily need to recompile the GNU C library since the
+only place where OPEN_MAX and FD_SETSIZE is really needed in the library
+itself is the size of fd_set which is used by select.
+
+The GNU C library is now (nearly) select free.  This means it internally has
+no limits imposed by the `fd_set' type.  Instead almost all places where the
+functionality is needed the `poll' function is used.
+
+If you increase the number of file descriptors in the kernel you don't need
+to recompile the C library.  The remaining select calls are in the RPC code.
+If your RPC daemons don't need more than FD_SETSIZE file descriptors, you
+don't need to change anything at all.
+
+{UD} You can always get the maximum number of file descriptors a process is
+allowed to have open at any time using
+
+	number = sysconf (_SC_OPEN_MAX);
+
+This will work even if the kernel limits change.
+
 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .